Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60f62bd0e81a46eb048cb9fea4285f99284410514710b0df8bf9fba4e0285198

Tx prefix hash: 6fb37835e4c342eeaf1e44bee5fbe8d52a6b3408bb976981726fbe8cd7a1ee6d
Tx public key: ee7fc38e7eb44eb2f62e83f1c579442530bcac60e69303a30b99705a24f44e8b
Timestamp: 1734920071 Timestamp [UCT]: 2024-12-23 02:14:31 Age [y:d:h:m:s]: 00:129:15:00:23
Block: 1181165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92413 RingCT/type: yes/0
Extra: 01ee7fc38e7eb44eb2f62e83f1c579442530bcac60e69303a30b99705a24f44e8b0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e6599729216c879d44df2295fd85326475598fd1a5913a2166793e0530a00a2 0.600000000000 1667582 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": 1181175, "vin": [ { "gen": { "height": 1181165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e6599729216c879d44df2295fd85326475598fd1a5913a2166793e0530a00a2" } } ], "extra": [ 1, 238, 127, 195, 142, 126, 180, 78, 178, 246, 46, 131, 241, 197, 121, 68, 37, 48, 188, 172, 96, 230, 147, 3, 163, 11, 153, 112, 90, 36, 244, 78, 139, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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