Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f353e9721b55da4d7f687b376240a707e549125fccf54036ce1969ad64ce0f41

Tx prefix hash: 859f18eb1afef81c6a0843fa98aa334298b88d6eaef6526166fbf96a5fd27a9e
Tx public key: 00e6e8f2b8e052d71df5d9142136805eb158b8c97b3e8747ef9f6c3df2dcc98d
Timestamp: 1750994444 Timestamp [UCT]: 2025-06-27 03:20:44 Age [y:d:h:m:s]: 00:142:05:33:16
Block: 1313601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99665 RingCT/type: yes/0
Extra: 0100e6e8f2b8e052d71df5d9142136805eb158b8c97b3e8747ef9f6c3df2dcc98d0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8dc0cfb8ae6774790004cb1d299f9e14c8a79898178fa45fdb54a6452b71067 0.600000000000 1801242 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": 1313611, "vin": [ { "gen": { "height": 1313601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8dc0cfb8ae6774790004cb1d299f9e14c8a79898178fa45fdb54a6452b71067" } } ], "extra": [ 1, 0, 230, 232, 242, 184, 224, 82, 215, 29, 245, 217, 20, 33, 54, 128, 94, 177, 88, 184, 201, 123, 62, 135, 71, 239, 159, 108, 61, 242, 220, 201, 141, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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