Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78572243723d8299604bfc5ee44d1d88edb6e8f93e76c6cade6a8df76bb2f373

Tx prefix hash: bf4e365804c80eb4a1cff99e22212b7fe5c3e995c04b0c3ea328773619740edf
Tx public key: fd34bd37a1fd5b1589720d45175835c13cc950bffdbfe721c2f7d1f1e2de00a1
Timestamp: 1702230254 Timestamp [UCT]: 2023-12-10 17:44:14 Age [y:d:h:m:s]: 01:333:04:06:47
Block: 910235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496978 RingCT/type: yes/0
Extra: 01fd34bd37a1fd5b1589720d45175835c13cc950bffdbfe721c2f7d1f1e2de00a102110000000be6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efc305c5f8047f4ee094e76ed47c73415744cc5e1ef56198279f3209030b15a2 0.600000000000 1367380 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": 910245, "vin": [ { "gen": { "height": 910235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efc305c5f8047f4ee094e76ed47c73415744cc5e1ef56198279f3209030b15a2" } } ], "extra": [ 1, 253, 52, 189, 55, 161, 253, 91, 21, 137, 114, 13, 69, 23, 88, 53, 193, 60, 201, 80, 191, 253, 191, 231, 33, 194, 247, 209, 241, 226, 222, 0, 161, 2, 17, 0, 0, 0, 11, 230, 210, 127, 156, 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