Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6224287a232b42bd840898ed2d26a07bc468ce4863e273bffb70edb650a8171

Tx prefix hash: d9f89b07ed1e872914dc7732baec7b15bc73ae0735382c660af49545cde6adfb
Tx public key: 79dd781790dc0a2401dfb2377b5a9b6193ef0618be190fd3b77e2b49e088b2eb
Timestamp: 1648330611 Timestamp [UCT]: 2022-03-26 21:36:51 Age [y:d:h:m:s]: 02:274:18:41:52
Block: 467044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 715943 RingCT/type: yes/0
Extra: 0179dd781790dc0a2401dfb2377b5a9b6193ef0618be190fd3b77e2b49e088b2eb02110000000d2e6b1fd5000000000000000000

1 output(s) for total of 17.397610461000 dcy

stealth address amount amount idx
00: 8be789cfbb9007ad21c134db04f5444ea29e077a32afd547de722eccf6255da5 17.397610461000 885471 of 0

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": 467054, "vin": [ { "gen": { "height": 467044 } } ], "vout": [ { "amount": 17397610461, "target": { "key": "8be789cfbb9007ad21c134db04f5444ea29e077a32afd547de722eccf6255da5" } } ], "extra": [ 1, 121, 221, 120, 23, 144, 220, 10, 36, 1, 223, 178, 55, 123, 90, 155, 97, 147, 239, 6, 24, 190, 25, 15, 211, 183, 126, 43, 73, 224, 136, 178, 235, 2, 17, 0, 0, 0, 13, 46, 107, 31, 213, 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