Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21d0ceaec88daf289a60c83cfae9cf2cc2281fc2d3dc2e1b01fa18ce56f7470d

Tx prefix hash: f5bc4e2c7a55ed9279dd7a721fa2e0ce3feccdc72ca4322aa3d43ce44735ae9f
Tx public key: 8e0341be25014d9af250af4b11f39aa35b4f9fa0513e6aae8142739e8f7831b1
Timestamp: 1760325190 Timestamp [UCT]: 2025-10-13 03:13:10 Age [y:d:h:m:s]: 00:102:03:40:43
Block: 1388757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73001 RingCT/type: yes/0
Extra: 018e0341be25014d9af250af4b11f39aa35b4f9fa0513e6aae8142739e8f7831b1021100000003df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87f705a695e2e8a6d49c0c3e75db365fca79317a03abb8200503cd089bb655ba 0.600000000000 1876980 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": 1388767, "vin": [ { "gen": { "height": 1388757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87f705a695e2e8a6d49c0c3e75db365fca79317a03abb8200503cd089bb655ba" } } ], "extra": [ 1, 142, 3, 65, 190, 37, 1, 77, 154, 242, 80, 175, 75, 17, 243, 154, 163, 91, 79, 159, 160, 81, 62, 106, 174, 129, 66, 115, 158, 143, 120, 49, 177, 2, 17, 0, 0, 0, 3, 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