Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f24f01b40b01ff5afdd18a3fd58b94b0b968e93214db201c5817e5b9a3ab0e7b

Tx prefix hash: beec21a845498886e06c18f5776b0b323da9e1b3f055da9aaea55929d8514c69
Tx public key: 0aa2d8abae3e4479360f28389b46ca3ab29746115b3608c7ec4cf41b7e7b5c4b
Timestamp: 1760575308 Timestamp [UCT]: 2025-10-16 00:41:48 Age [y:d:h:m:s]: 00:106:04:43:25
Block: 1390821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75865 RingCT/type: yes/0
Extra: 010aa2d8abae3e4479360f28389b46ca3ab29746115b3608c7ec4cf41b7e7b5c4b0211000000045dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be1e2ad47dfff7aa2d8a1c77145c8c2c194b0db20797fffef75a92d34f9afe90 0.600000000000 1879068 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": 1390831, "vin": [ { "gen": { "height": 1390821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be1e2ad47dfff7aa2d8a1c77145c8c2c194b0db20797fffef75a92d34f9afe90" } } ], "extra": [ 1, 10, 162, 216, 171, 174, 62, 68, 121, 54, 15, 40, 56, 155, 70, 202, 58, 178, 151, 70, 17, 91, 54, 8, 199, 236, 76, 244, 27, 126, 123, 92, 75, 2, 17, 0, 0, 0, 4, 93, 251, 190, 42, 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