Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edddecbe4642f32dc7bbb47ebbfb91a982511c459c7c375d30e87c8bdb7b2878

Tx prefix hash: f76bbf4f9d76d6f97cc8b6fb6d0a2bf70d7591673373baf290a5502201415d9e
Tx public key: a1ed6017f45e19277b423cecacdc8357992b493c0e32d87e9af66058891ea885
Timestamp: 1736708700 Timestamp [UCT]: 2025-01-12 19:05:00 Age [y:d:h:m:s]: 00:156:12:03:24
Block: 1195932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111563 RingCT/type: yes/0
Extra: 01a1ed6017f45e19277b423cecacdc8357992b493c0e32d87e9af66058891ea8850211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78627e3e3ee12c1c184ca27734b0d5a9b0d74f8ba7d03e8718b316cce0bc2d02 0.600000000000 1682525 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": 1195942, "vin": [ { "gen": { "height": 1195932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78627e3e3ee12c1c184ca27734b0d5a9b0d74f8ba7d03e8718b316cce0bc2d02" } } ], "extra": [ 1, 161, 237, 96, 23, 244, 94, 25, 39, 123, 66, 60, 236, 172, 220, 131, 87, 153, 43, 73, 60, 14, 50, 216, 126, 154, 246, 96, 88, 137, 30, 168, 133, 2, 17, 0, 0, 0, 1, 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