Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2081725b8efd060cd2407889a8e7e8da6b353fc408eaeb52659a8b76f52296d

Tx prefix hash: b17b8ceb0c001fd8e8c09a09cfb727f47cb9b7057e2d15895b109fba28390882
Tx public key: 0110d371bd04417b6ab1805a0d5e3709bc918861b6596cfc8e508a89b4bc8a88
Timestamp: 1735758085 Timestamp [UCT]: 2025-01-01 19:01:25 Age [y:d:h:m:s]: 00:169:04:24:44
Block: 1188063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120613 RingCT/type: yes/0
Extra: 010110d371bd04417b6ab1805a0d5e3709bc918861b6596cfc8e508a89b4bc8a8802110000000e1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8ddb37ad08affb4cfb9df991da2a8c70238f70d62297e4de02fd02ab6912db6 0.600000000000 1674562 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": 1188073, "vin": [ { "gen": { "height": 1188063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8ddb37ad08affb4cfb9df991da2a8c70238f70d62297e4de02fd02ab6912db6" } } ], "extra": [ 1, 1, 16, 211, 113, 189, 4, 65, 123, 106, 177, 128, 90, 13, 94, 55, 9, 188, 145, 136, 97, 182, 89, 108, 252, 142, 80, 138, 137, 180, 188, 138, 136, 2, 17, 0, 0, 0, 14, 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