Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4b68b06b6a8ff65d2f7021bf93e5f5f6f42b63f095e3665191df2b0574fb054

Tx prefix hash: 50e6669f4b72bd92fecfa18383096df93f231ab365467d1cc61a6ddc41cb6c55
Tx public key: d108d2bf15e470bdab46c3abf76d621cfc06d0648650ad8cecbbb1a54fc15ac7
Timestamp: 1739186762 Timestamp [UCT]: 2025-02-10 11:26:02 Age [y:d:h:m:s]: 00:323:02:04:21
Block: 1216187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228718 RingCT/type: yes/0
Extra: 01d108d2bf15e470bdab46c3abf76d621cfc06d0648650ad8cecbbb1a54fc15ac70211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c77c976fb1f8883be4457017a911e50d119de76f42a70c0b628923e7dba53d44 0.600000000000 1702988 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": 1216197, "vin": [ { "gen": { "height": 1216187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c77c976fb1f8883be4457017a911e50d119de76f42a70c0b628923e7dba53d44" } } ], "extra": [ 1, 209, 8, 210, 191, 21, 228, 112, 189, 171, 70, 195, 171, 247, 109, 98, 28, 252, 6, 208, 100, 134, 80, 173, 140, 236, 187, 177, 165, 79, 193, 90, 199, 2, 17, 0, 0, 0, 3, 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