Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2eef28f95bb11db14a6c6c1db8e73935df35d9f82826666f34a5636abfa95ca5

Tx prefix hash: 253297f67a775a0af2bd5ee3e7595bc3a4f9c03bbc723da216d69940d634a614
Tx public key: 8dce0493cdd2cdb10df352df3b23543d1e4b4ae4662345688ed180047fd89d3c
Timestamp: 1702034706 Timestamp [UCT]: 2023-12-08 11:25:06 Age [y:d:h:m:s]: 01:192:09:21:06
Block: 908606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398573 RingCT/type: yes/0
Extra: 018dce0493cdd2cdb10df352df3b23543d1e4b4ae4662345688ed180047fd89d3c021100000007faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 130bab0fa55bd4c4485a4082e5b1ef98eafa1cf944d33395018548d730e2faea 0.600000000000 1365651 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": 908616, "vin": [ { "gen": { "height": 908606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "130bab0fa55bd4c4485a4082e5b1ef98eafa1cf944d33395018548d730e2faea" } } ], "extra": [ 1, 141, 206, 4, 147, 205, 210, 205, 177, 13, 243, 82, 223, 59, 35, 84, 61, 30, 75, 74, 228, 102, 35, 69, 104, 142, 209, 128, 4, 127, 216, 157, 60, 2, 17, 0, 0, 0, 7, 250, 243, 92, 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