Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a391bba119a22b2a501e5e61bc5ffe83f4b84533c8687a0711ca52c2d36f2a6

Tx prefix hash: 2238603b2e9c430138e901f209e38b0eab82bd698f2dcde4a68acde417e59286
Tx public key: 567e34e56efde64190c2c59fbe94c49fd308a9b7e1afa2e44876ee063ca96438
Timestamp: 1700811243 Timestamp [UCT]: 2023-11-24 07:34:03 Age [y:d:h:m:s]: 01:053:08:37:18
Block: 898466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299520 RingCT/type: yes/0
Extra: 01567e34e56efde64190c2c59fbe94c49fd308a9b7e1afa2e44876ee063ca964380211000000024b8f5122000000000000000000

1 output(s) for total of 0.647156260000 dcy

stealth address amount amount idx
00: 0389dcc5eb1c80378fcb3a2b01ed1456dc5d135bc8214f5b1dda404bd5233d45 0.647156260000 1354883 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": 898476, "vin": [ { "gen": { "height": 898466 } } ], "vout": [ { "amount": 647156260, "target": { "key": "0389dcc5eb1c80378fcb3a2b01ed1456dc5d135bc8214f5b1dda404bd5233d45" } } ], "extra": [ 1, 86, 126, 52, 229, 110, 253, 230, 65, 144, 194, 197, 159, 190, 148, 196, 159, 211, 8, 169, 183, 225, 175, 162, 228, 72, 118, 238, 6, 60, 169, 100, 56, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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