Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ef61a89fc8c3a8bf5516474089d40b7151c28a7608cf490d58ca4dea7b6838f

Tx prefix hash: 81eb4bf65c198381ed2ebd9a105f461558d5e49a3e74215314d4c292139c4778
Tx public key: 01647ce8608d2f6311a4413b6b0cdae7e8e817407bde525435f4c292114b8688
Timestamp: 1702929458 Timestamp [UCT]: 2023-12-18 19:57:38 Age [y:d:h:m:s]: 01:144:09:14:44
Block: 916030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364339 RingCT/type: yes/0
Extra: 0101647ce8608d2f6311a4413b6b0cdae7e8e817407bde525435f4c292114b8688021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1b7672f563f74cf1c4979149cb0c5d83618c6edcc156bf9007b1e937b1c22f3 0.600000000000 1373488 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": 916040, "vin": [ { "gen": { "height": 916030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1b7672f563f74cf1c4979149cb0c5d83618c6edcc156bf9007b1e937b1c22f3" } } ], "extra": [ 1, 1, 100, 124, 232, 96, 141, 47, 99, 17, 164, 65, 59, 107, 12, 218, 231, 232, 232, 23, 64, 123, 222, 82, 84, 53, 244, 194, 146, 17, 75, 134, 136, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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