Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccf775d8cffe3be142c4aab6facf0f6eaaa56a3e1973be813909f2cb9061c80e

Tx prefix hash: ad9f683ce6fabb7344037db09cfd9cbb1225278915849806ed63f2e0743da26c
Tx public key: 0616f11f5c8e2a748f4b8c345d50bf01bd9a7f68dc4c5f31f5136b52fd72d767
Timestamp: 1758680122 Timestamp [UCT]: 2025-09-24 02:15:22 Age [y:d:h:m:s]: 00:043:20:00:12
Block: 1375113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31392 RingCT/type: yes/0
Extra: 010616f11f5c8e2a748f4b8c345d50bf01bd9a7f68dc4c5f31f5136b52fd72d767021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62a4be6530dc414b8c7b45464c73a50df205eb674e84789d3be18585f65d99d9 0.600000000000 1863198 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": 1375123, "vin": [ { "gen": { "height": 1375113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62a4be6530dc414b8c7b45464c73a50df205eb674e84789d3be18585f65d99d9" } } ], "extra": [ 1, 6, 22, 241, 31, 92, 142, 42, 116, 143, 75, 140, 52, 93, 80, 191, 1, 189, 154, 127, 104, 220, 76, 95, 49, 245, 19, 107, 82, 253, 114, 215, 103, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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