Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84946fbfed825319f0eb4f1b83a3c05e002f3034ee71a0b29b7962dc22bab900

Tx prefix hash: fec9d118a6dd1a2cf830aae07b4a675c00a0b7e4a99eaad89a6de3b8d92e210b
Tx public key: 06be7819955cc542fe368627a9beb272b066e022e52a7d85f64f8ea63b7e8551
Timestamp: 1752001333 Timestamp [UCT]: 2025-07-08 19:02:13 Age [y:d:h:m:s]: 00:142:13:28:27
Block: 1321497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100347 RingCT/type: yes/0
Extra: 0106be7819955cc542fe368627a9beb272b066e022e52a7d85f64f8ea63b7e855102110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b974c531bc3ca466e88e12a941936f9d40ba7c6e33bee702fe95a6a9dc1dbc46 0.600000000000 1809204 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": 1321507, "vin": [ { "gen": { "height": 1321497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b974c531bc3ca466e88e12a941936f9d40ba7c6e33bee702fe95a6a9dc1dbc46" } } ], "extra": [ 1, 6, 190, 120, 25, 149, 92, 197, 66, 254, 54, 134, 39, 169, 190, 178, 114, 176, 102, 224, 34, 229, 42, 125, 133, 246, 79, 142, 166, 59, 126, 133, 81, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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