Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cc406eb4ca7ec90c9250849cd87381550dde746bda3ff2de74e7968cd1c6597

Tx prefix hash: 042dc581866dcb413a1bf47ef3e4fbf781833565bfddf19c84f5c8b22cfcd515
Tx public key: 8725a3c38efe5d2d8e74c5aed8dd8cf33e9768114195d61cf09712bf6c31374a
Timestamp: 1731359236 Timestamp [UCT]: 2024-11-11 21:07:16 Age [y:d:h:m:s]: 00:142:17:14:18
Block: 1151623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101838 RingCT/type: yes/0
Extra: 018725a3c38efe5d2d8e74c5aed8dd8cf33e9768114195d61cf09712bf6c31374a02110000000ad8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba3311c0e78224a0aed6031c2dd5038fb4ea7e771d6bab0b0539b1ce3d266de2 0.600000000000 1637192 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": 1151633, "vin": [ { "gen": { "height": 1151623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba3311c0e78224a0aed6031c2dd5038fb4ea7e771d6bab0b0539b1ce3d266de2" } } ], "extra": [ 1, 135, 37, 163, 195, 142, 254, 93, 45, 142, 116, 197, 174, 216, 221, 140, 243, 62, 151, 104, 17, 65, 149, 214, 28, 240, 151, 18, 191, 108, 49, 55, 74, 2, 17, 0, 0, 0, 10, 216, 231, 210, 65, 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