Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d31d7ee5c5307223de69b902e10e181ca4f002d254e280dad5cd73d1c66a232

Tx prefix hash: 632060a8f6a7909dcd757861186c3ee31d3406a77942d7c22e411b45d81de574
Tx public key: 0dff13d6298c4a2079c789ea9abf94039d9c81e7fabdfc187a8728168ade3c61
Timestamp: 1712611776 Timestamp [UCT]: 2024-04-08 21:29:36 Age [y:d:h:m:s]: 01:037:14:50:56
Block: 996281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287880 RingCT/type: yes/0
Extra: 010dff13d6298c4a2079c789ea9abf94039d9c81e7fabdfc187a8728168ade3c610211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f51f1473921d2a9a028710394311b45dceb83fb6f1240a0f8bdec7baf61ee682 0.600000000000 1456697 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": 996291, "vin": [ { "gen": { "height": 996281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f51f1473921d2a9a028710394311b45dceb83fb6f1240a0f8bdec7baf61ee682" } } ], "extra": [ 1, 13, 255, 19, 214, 41, 140, 74, 32, 121, 199, 137, 234, 154, 191, 148, 3, 157, 156, 129, 231, 250, 189, 252, 24, 122, 135, 40, 22, 138, 222, 60, 97, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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