Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c3af265b4db548f78d3b1e7eb84a78337ffad9ed3a612600ac5a7138cd8269a

Tx prefix hash: 1a1e831b4c55297a31a8515477094bf1c27c64b2ead9c56537c210019742cc34
Tx public key: f1c5d9f43dec9fe8e898e37789d8d6b3daf01abf5c1022265e2da836e31c6a9d
Timestamp: 1731611952 Timestamp [UCT]: 2024-11-14 19:19:12 Age [y:d:h:m:s]: 00:216:19:36:20
Block: 1153741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154695 RingCT/type: yes/0
Extra: 01f1c5d9f43dec9fe8e898e37789d8d6b3daf01abf5c1022265e2da836e31c6a9d0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e1ef631316eef04bbd11d93ac4f8caf52fd8465caab5a1083604e5b25697749 0.600000000000 1639352 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": 1153751, "vin": [ { "gen": { "height": 1153741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e1ef631316eef04bbd11d93ac4f8caf52fd8465caab5a1083604e5b25697749" } } ], "extra": [ 1, 241, 197, 217, 244, 61, 236, 159, 232, 232, 152, 227, 119, 137, 216, 214, 179, 218, 240, 26, 191, 92, 16, 34, 38, 94, 45, 168, 54, 227, 28, 106, 157, 2, 17, 0, 0, 0, 2, 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