Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9043a7e8cd6a8f589462bb44da8af2e79821c2a2eef71031afe854653b3c9b2a

Tx prefix hash: b6f1733ee40e296f7eb40a30f1a95333ffde7434dd4e39df49b227dad0e70da5
Tx public key: c32fc1c1552e1ae84e4a99b8cb5b3d151a3feafd7dc7ca3b62c7d4ace2f64b2e
Timestamp: 1721812380 Timestamp [UCT]: 2024-07-24 09:13:00 Age [y:d:h:m:s]: 01:131:14:14:14
Block: 1072571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352594 RingCT/type: yes/0
Extra: 01c32fc1c1552e1ae84e4a99b8cb5b3d151a3feafd7dc7ca3b62c7d4ace2f64b2e021100000013e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21a940c9613eda9e010e9cf6baefa0b7a8896f5a031d268431d3468533dc64b9 0.600000000000 1545050 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": 1072581, "vin": [ { "gen": { "height": 1072571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21a940c9613eda9e010e9cf6baefa0b7a8896f5a031d268431d3468533dc64b9" } } ], "extra": [ 1, 195, 47, 193, 193, 85, 46, 26, 232, 78, 74, 153, 184, 203, 91, 61, 21, 26, 63, 234, 253, 125, 199, 202, 59, 98, 199, 212, 172, 226, 246, 75, 46, 2, 17, 0, 0, 0, 19, 233, 20, 221, 21, 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