Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07530e948b918d73bd5af7474153264a3e0a367f1724ef836f151c9052a6ddc5

Tx prefix hash: e2cf5189dca2ea120e1a2d6326d5066f4626bb8a90d54351bb67240b708047f6
Tx public key: cafa246f48d6d738be2fe51d17bbb635b6fddd98e6b470ca46bbc89340e5f46e
Timestamp: 1725892836 Timestamp [UCT]: 2024-09-09 14:40:36 Age [y:d:h:m:s]: 00:166:13:06:31
Block: 1106408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118829 RingCT/type: yes/0
Extra: 01cafa246f48d6d738be2fe51d17bbb635b6fddd98e6b470ca46bbc89340e5f46e02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 489432e771069c0bda51156d2262a2d5400d875be14f5e591cb6c9b52ba6b1ee 0.600000000000 1584007 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": 1106418, "vin": [ { "gen": { "height": 1106408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "489432e771069c0bda51156d2262a2d5400d875be14f5e591cb6c9b52ba6b1ee" } } ], "extra": [ 1, 202, 250, 36, 111, 72, 214, 215, 56, 190, 47, 229, 29, 23, 187, 182, 53, 182, 253, 221, 152, 230, 180, 112, 202, 70, 187, 200, 147, 64, 229, 244, 110, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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