Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 637f1113c350693578bef69c760bb7a100bf9c9e294d6384b0df0eb69bbfd01a

Tx prefix hash: e6b9b703fb2d5eeb3ca0f9222efffcc80c56fc2eeeabdee3902e3a850cba7f55
Tx public key: 523808723460bfff0c9419027849f74c3f5b6e1463e54b1daf83e66f010e21ed
Timestamp: 1715223904 Timestamp [UCT]: 2024-05-09 03:05:04 Age [y:d:h:m:s]: 01:267:01:25:13
Block: 1017968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449402 RingCT/type: yes/0
Extra: 01523808723460bfff0c9419027849f74c3f5b6e1463e54b1daf83e66f010e21ed0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7339a48bcfab86a9cb0925dfe628277b911c2ea458c02c2589e7f623534dfcfb 0.600000000000 1481753 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": 1017978, "vin": [ { "gen": { "height": 1017968 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7339a48bcfab86a9cb0925dfe628277b911c2ea458c02c2589e7f623534dfcfb" } } ], "extra": [ 1, 82, 56, 8, 114, 52, 96, 191, 255, 12, 148, 25, 2, 120, 73, 247, 76, 63, 91, 110, 20, 99, 229, 75, 29, 175, 131, 230, 111, 1, 14, 33, 237, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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