Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c980d947fab8617109566ed7e70864d6549319a748029b9013f76d253cb94034

Tx prefix hash: c699ee571c5e808c66002b9990e0ec3253a522e4ab5cb19f652bd3ed0e905621
Tx public key: 471d3f90c56b0cbe21e728dcd1b5603c0cb1311aea9a781970d8f35a92f62dd8
Timestamp: 1715098941 Timestamp [UCT]: 2024-05-07 16:22:21 Age [y:d:h:m:s]: 00:330:21:59:13
Block: 1016927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236534 RingCT/type: yes/0
Extra: 01471d3f90c56b0cbe21e728dcd1b5603c0cb1311aea9a781970d8f35a92f62dd80211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52e2a7fd6baa5416519be63dd866284cdca8300b26ffed6316e333560bd7b055 0.600000000000 1480656 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": 1016937, "vin": [ { "gen": { "height": 1016927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52e2a7fd6baa5416519be63dd866284cdca8300b26ffed6316e333560bd7b055" } } ], "extra": [ 1, 71, 29, 63, 144, 197, 107, 12, 190, 33, 231, 40, 220, 209, 181, 96, 60, 12, 177, 49, 26, 234, 154, 120, 25, 112, 216, 243, 90, 146, 246, 45, 216, 2, 17, 0, 0, 0, 5, 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