Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e834c445b057f640f0f01e90d96b3b3ea47cb23025517bce30319f64fed33329

Tx prefix hash: 330b0bb488c915f08ab62337ad939ddbbfc9a269b1a2fe5af6b28f0b780915c8
Tx public key: 5abc961bd887447a2d3671c88ba4feb3e80e3a8129f1f6338825b8cf3bb77f04
Timestamp: 1717255518 Timestamp [UCT]: 2024-06-01 15:25:18 Age [y:d:h:m:s]: 01:159:20:01:08
Block: 1034807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372803 RingCT/type: yes/0
Extra: 015abc961bd887447a2d3671c88ba4feb3e80e3a8129f1f6338825b8cf3bb77f04021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75d9a7861a55218287da5dbf093bbe8717aa5d0266923d797d6803faa5e9370e 0.600000000000 1503326 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": 1034817, "vin": [ { "gen": { "height": 1034807 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75d9a7861a55218287da5dbf093bbe8717aa5d0266923d797d6803faa5e9370e" } } ], "extra": [ 1, 90, 188, 150, 27, 216, 135, 68, 122, 45, 54, 113, 200, 139, 164, 254, 179, 232, 14, 58, 129, 41, 241, 246, 51, 136, 37, 184, 207, 59, 183, 127, 4, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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