Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: faf3ca9f2b2fb2d9b522363aa1f4d17d60cc5f24dc3350a42b02f30506747027

Tx prefix hash: 0e8696b4485a46388f806bd2a5ee61d25d8c9aed08c8edd9fa34bde6b0ac633c
Tx public key: a19a64bac600f51950cd81fb3659b70f37e3593c936b5e7c742f896084e9bf99
Timestamp: 1754403915 Timestamp [UCT]: 2025-08-05 14:25:15 Age [y:d:h:m:s]: 00:053:04:43:40
Block: 1340843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36921 RingCT/type: yes/0
Extra: 01a19a64bac600f51950cd81fb3659b70f37e3593c936b5e7c742f896084e9bf99021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3100f714a2de23f08193dcd0b55e7668d88cee6690eb73dd58fecba84ac8cbc3 0.600000000000 1828664 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": 1340853, "vin": [ { "gen": { "height": 1340843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3100f714a2de23f08193dcd0b55e7668d88cee6690eb73dd58fecba84ac8cbc3" } } ], "extra": [ 1, 161, 154, 100, 186, 198, 0, 245, 25, 80, 205, 129, 251, 54, 89, 183, 15, 55, 227, 89, 60, 147, 107, 94, 124, 116, 47, 137, 96, 132, 233, 191, 153, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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