Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 870670f84c512bfa94b35f09710fbb3024ac1237fb23caa48963f406728fd15c

Tx prefix hash: 5ba3f6180fa6af3c9917738c446a9fdbaba6867451bf56e12ddbccb2c6023794
Tx public key: a7eec9a9cb7f5c5e8a8af6cd4fd067e3da666c2e6b2f5849f68cac29cc66f61d
Timestamp: 1648484121 Timestamp [UCT]: 2022-03-28 16:15:21 Age [y:d:h:m:s]: 03:036:02:16:56
Block: 468300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 806036 RingCT/type: yes/0
Extra: 01a7eec9a9cb7f5c5e8a8af6cd4fd067e3da666c2e6b2f5849f68cac29cc66f61d021100000003d3fcec30000000000000000000

1 output(s) for total of 17.231693109000 dcy

stealth address amount amount idx
00: beb1b5a52dd8e94ebc2d914a4a11cd88db7557699e244c25188d3089694606b5 17.231693109000 886994 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": 468310, "vin": [ { "gen": { "height": 468300 } } ], "vout": [ { "amount": 17231693109, "target": { "key": "beb1b5a52dd8e94ebc2d914a4a11cd88db7557699e244c25188d3089694606b5" } } ], "extra": [ 1, 167, 238, 201, 169, 203, 127, 92, 94, 138, 138, 246, 205, 79, 208, 103, 227, 218, 102, 108, 46, 107, 47, 88, 73, 246, 140, 172, 41, 204, 102, 246, 29, 2, 17, 0, 0, 0, 3, 211, 252, 236, 48, 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