Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d28af4abe2148e946781c04676db435cd97f9d672e935a96c79f602453b6b352

Tx prefix hash: 8557e173f6534d0fbab3cd244db427c6dc125ee7acc63d97c2c943a744c8c5f8
Tx public key: f9e23cc759a3144ce5b39d4c9147f96e8881616d161078db2e43e1ce7a5e2b18
Timestamp: 1740320291 Timestamp [UCT]: 2025-02-23 14:18:11 Age [y:d:h:m:s]: 00:226:17:18:11
Block: 1225548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159753 RingCT/type: yes/0
Extra: 01f9e23cc759a3144ce5b39d4c9147f96e8881616d161078db2e43e1ce7a5e2b1802110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 099cdd212d2e47e97df280448051d126aec8873853aae14310e04d8d1135c997 0.600000000000 1712413 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": 1225558, "vin": [ { "gen": { "height": 1225548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "099cdd212d2e47e97df280448051d126aec8873853aae14310e04d8d1135c997" } } ], "extra": [ 1, 249, 226, 60, 199, 89, 163, 20, 76, 229, 179, 157, 76, 145, 71, 249, 110, 136, 129, 97, 109, 22, 16, 120, 219, 46, 67, 225, 206, 122, 94, 43, 24, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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