Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfa0e88c76d9349d2a9aee4722eebad09fc0cff7028d3439afe9823f3f026847

Tx prefix hash: ae7e0fb636c25437ebf29cade7cdcc4b82fa66d0b32392a2bf465a97f83aef5f
Tx public key: 14c6dcb4c48d9796f8b9fb03b7bc92f4b116e664abbc3560bc48e1d4670295e6
Timestamp: 1764093888 Timestamp [UCT]: 2025-11-25 18:04:48 Age [y:d:h:m:s]: 00:042:18:17:15
Block: 1419989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30621 RingCT/type: yes/0
Extra: 0114c6dcb4c48d9796f8b9fb03b7bc92f4b116e664abbc3560bc48e1d4670295e6021100000001defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58cbaa63e4681fa808cc7ca3fe01300e90555ddb540b971d3921c9aee7ab180d 0.600000000000 1908530 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": 1419999, "vin": [ { "gen": { "height": 1419989 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58cbaa63e4681fa808cc7ca3fe01300e90555ddb540b971d3921c9aee7ab180d" } } ], "extra": [ 1, 20, 198, 220, 180, 196, 141, 151, 150, 248, 185, 251, 3, 183, 188, 146, 244, 177, 22, 230, 100, 171, 188, 53, 96, 188, 72, 225, 212, 103, 2, 149, 230, 2, 17, 0, 0, 0, 1, 222, 251, 143, 24, 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