Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53b661b03bfe716013029c8c3064c0e4dc1f8df426af38f3a3d7da057a9eaa03

Tx prefix hash: dd663575893dad7345c011b3b50e2660e0bc6e8f50ab564d691807330e9557f8
Tx public key: eeaa69b856ab8ec98bbc41265a3e7f4027ab87e381a0eefbef833b525608afe6
Timestamp: 1748632081 Timestamp [UCT]: 2025-05-30 19:08:01 Age [y:d:h:m:s]: 00:173:12:53:28
Block: 1294392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121715 RingCT/type: yes/0
Extra: 01eeaa69b856ab8ec98bbc41265a3e7f4027ab87e381a0eefbef833b525608afe602110000000743846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05c2d8d108ef26c49bfdda961cf1bedf17068d95b0b5d7972e79fcc9439dce71 0.600000000000 1781887 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": 1294402, "vin": [ { "gen": { "height": 1294392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05c2d8d108ef26c49bfdda961cf1bedf17068d95b0b5d7972e79fcc9439dce71" } } ], "extra": [ 1, 238, 170, 105, 184, 86, 171, 142, 201, 139, 188, 65, 38, 90, 62, 127, 64, 39, 171, 135, 227, 129, 160, 238, 251, 239, 131, 59, 82, 86, 8, 175, 230, 2, 17, 0, 0, 0, 7, 67, 132, 109, 102, 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