Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01bd0d6c04586ad8d55eee6118c2c0ecb4588d8f9dabc68532866cfff2be466a

Tx prefix hash: e107bfaed255383cf3c72af8c44b0c30cb7d380eec59477624d6c53f07a5c4f2
Tx public key: defd1e9677e237828d2ebc943d70cd159cfe0cb875e4aeb08b6e115dd1605b4c
Timestamp: 1760800451 Timestamp [UCT]: 2025-10-18 15:14:11 Age [y:d:h:m:s]: 00:082:19:30:31
Block: 1392706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59279 RingCT/type: yes/0
Extra: 01defd1e9677e237828d2ebc943d70cd159cfe0cb875e4aeb08b6e115dd1605b4c021100000007df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d41927b5893088148bfac9274a9b1cf7190df245e181113fa2021b0ec927abb 0.600000000000 1880959 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": 1392716, "vin": [ { "gen": { "height": 1392706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d41927b5893088148bfac9274a9b1cf7190df245e181113fa2021b0ec927abb" } } ], "extra": [ 1, 222, 253, 30, 150, 119, 226, 55, 130, 141, 46, 188, 148, 61, 112, 205, 21, 156, 254, 12, 184, 117, 228, 174, 176, 139, 110, 17, 93, 209, 96, 91, 76, 2, 17, 0, 0, 0, 7, 223, 90, 36, 122, 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