Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69b41f9e61983b90f171712c17216748007249375fc623e603b53c062f66e450

Tx prefix hash: b6e67abbb91741377e76cbe1d9322730281389bac3b02eb9b773a0dbe9b4db1f
Tx public key: b962b142e8f7f4aede3a8813c2cac1d0d2967934a40005a0dbdb6e0c62ec472e
Timestamp: 1763082162 Timestamp [UCT]: 2025-11-14 01:02:42 Age [y:d:h:m:s]: 00:039:23:03:47
Block: 1411598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28603 RingCT/type: yes/0
Extra: 01b962b142e8f7f4aede3a8813c2cac1d0d2967934a40005a0dbdb6e0c62ec472e021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 253c84da6e2037f880865ec09c386a4a5cfea126f55460ba03f8244ffff0c497 0.600000000000 1900061 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": 1411608, "vin": [ { "gen": { "height": 1411598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "253c84da6e2037f880865ec09c386a4a5cfea126f55460ba03f8244ffff0c497" } } ], "extra": [ 1, 185, 98, 177, 66, 232, 247, 244, 174, 222, 58, 136, 19, 194, 202, 193, 208, 210, 150, 121, 52, 164, 0, 5, 160, 219, 219, 110, 12, 98, 236, 71, 46, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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