Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37ef021de777b1770db406fc5c409c07018879dfea697177c955cf3adc501303

Tx prefix hash: 08e3f102fee7039463ca974b4f8914bbc820a7b5b822726a23195e1ec4b5be6e
Tx public key: fcede9c8911c45597d4d8fe64f75ec4086351e2e885dbc1e7a99a6297a715255
Timestamp: 1617486093 Timestamp [UCT]: 2021-04-03 21:41:33 Age [y:d:h:m:s]: 03:229:13:46:07
Block: 232665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 923697 RingCT/type: yes/0
Extra: 01fcede9c8911c45597d4d8fe64f75ec4086351e2e885dbc1e7a99a6297a71525502110000000a3a645b90000000000000000000

1 output(s) for total of 104.014135667000 dcy

stealth address amount amount idx
00: 24a31e467e3db0f2b1b6ebf21d2d1546fea9417dd41d4ac262b4a8f7777decd8 104.014135667000 483369 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": 232675, "vin": [ { "gen": { "height": 232665 } } ], "vout": [ { "amount": 104014135667, "target": { "key": "24a31e467e3db0f2b1b6ebf21d2d1546fea9417dd41d4ac262b4a8f7777decd8" } } ], "extra": [ 1, 252, 237, 233, 200, 145, 28, 69, 89, 125, 77, 143, 230, 79, 117, 236, 64, 134, 53, 30, 46, 136, 93, 188, 30, 122, 153, 166, 41, 122, 113, 82, 85, 2, 17, 0, 0, 0, 10, 58, 100, 91, 144, 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