Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45dc419eda1cb51ebfc4f2e4f1448bb01241c559eccade821c5ddc17d085747d

Tx prefix hash: 69006401644b34ce5fe9abb158afc97917fb2712cd2aac8538c880bab20b9ae1
Tx public key: a807b5de9483f9e56f200b9568c107ae4f4d746e6d0d683fc188d6feecb5a9c5
Timestamp: 1763669863 Timestamp [UCT]: 2025-11-20 20:17:43 Age [y:d:h:m:s]: 00:032:21:22:07
Block: 1416462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23550 RingCT/type: yes/0
Extra: 01a807b5de9483f9e56f200b9568c107ae4f4d746e6d0d683fc188d6feecb5a9c502110000000170609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0d1759c479fd93fac4131b10bff9cb49e45e6091c2e2916d72d81eb0aff1d61 0.600000000000 1904981 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": 1416472, "vin": [ { "gen": { "height": 1416462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0d1759c479fd93fac4131b10bff9cb49e45e6091c2e2916d72d81eb0aff1d61" } } ], "extra": [ 1, 168, 7, 181, 222, 148, 131, 249, 229, 111, 32, 11, 149, 104, 193, 7, 174, 79, 77, 116, 110, 109, 13, 104, 63, 193, 136, 214, 254, 236, 181, 169, 197, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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