Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dabb7ca9550102d65d2c5c2e0ca132326cc20e3e30a1466d7ce028b177a526bc

Tx prefix hash: b9f51d5868a71c0877caf8415c083482fbea35601cba5aea920e2c2680f1c456
Tx public key: a8ab42349750a01dafb23fad6fd18ea1bc0fab92b7d58966257e83aaa798e2c3
Timestamp: 1730382954 Timestamp [UCT]: 2024-10-31 13:55:54 Age [y:d:h:m:s]: 00:024:01:29:52
Block: 1143559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17224 RingCT/type: yes/0
Extra: 01a8ab42349750a01dafb23fad6fd18ea1bc0fab92b7d58966257e83aaa798e2c30211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10363efbf8e57da95d55e5e6b90348547edc7d879b880299ed99f73b9ea816c8 0.600000000000 1627472 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": 1143569, "vin": [ { "gen": { "height": 1143559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10363efbf8e57da95d55e5e6b90348547edc7d879b880299ed99f73b9ea816c8" } } ], "extra": [ 1, 168, 171, 66, 52, 151, 80, 160, 29, 175, 178, 63, 173, 111, 209, 142, 161, 188, 15, 171, 146, 183, 213, 137, 102, 37, 126, 131, 170, 167, 152, 226, 195, 2, 17, 0, 0, 0, 7, 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