Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1942bc51e0d3a983c60af52c28141a14db9ccf995a3996f8f2b66a5bc0f174e0

Tx prefix hash: aafbb668b0084a1a91fe2c4e3b868f7cadec305fcd549357783dc5be87d0e2c7
Tx public key: 09fea74167807a7b91a3f88f7f91a7e1c34fd49023e5dbb2490ead06727f03da
Timestamp: 1762434146 Timestamp [UCT]: 2025-11-06 13:02:26 Age [y:d:h:m:s]: 00:015:04:48:10
Block: 1406219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10886 RingCT/type: yes/0
Extra: 0109fea74167807a7b91a3f88f7f91a7e1c34fd49023e5dbb2490ead06727f03da021100000001df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d1b0799a0d1a04cb0c88f30dff562e1d2c0b1b7bb671f376a55d40dc68ebbbd 0.600000000000 1894602 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": 1406229, "vin": [ { "gen": { "height": 1406219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d1b0799a0d1a04cb0c88f30dff562e1d2c0b1b7bb671f376a55d40dc68ebbbd" } } ], "extra": [ 1, 9, 254, 167, 65, 103, 128, 122, 123, 145, 163, 248, 143, 127, 145, 167, 225, 195, 79, 212, 144, 35, 229, 219, 178, 73, 14, 173, 6, 114, 127, 3, 218, 2, 17, 0, 0, 0, 1, 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