Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 51cadc13f0c8ac9582433d2ad344d2e500143cb5ed3bd515c84cc597ddf1c684

Tx prefix hash: dd101ab803e3b1f6edfe3b47c83de8bedd0ac78366eb4bf788641e9745eafeeb
Tx public key: 7c01a6acd798190a31bc6b7f9ec1d28913b713f04cd8350bea839c2adfded2dd
Timestamp: 1717535428 Timestamp [UCT]: 2024-06-04 21:10:28 Age [y:d:h:m:s]: 00:345:23:05:24
Block: 1037129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247271 RingCT/type: yes/0
Extra: 017c01a6acd798190a31bc6b7f9ec1d28913b713f04cd8350bea839c2adfded2dd02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c91f3d47f279b85b5b0c1c294a7f43ffb088222bfd95c49a5f818277d74351b5 0.600000000000 1505660 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1037139, "vin": [ { "gen": { "height": 1037129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c91f3d47f279b85b5b0c1c294a7f43ffb088222bfd95c49a5f818277d74351b5" } } ], "extra": [ 1, 124, 1, 166, 172, 215, 152, 25, 10, 49, 188, 107, 127, 158, 193, 210, 137, 19, 183, 19, 240, 76, 216, 53, 11, 234, 131, 156, 42, 223, 222, 210, 221, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8