Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6941e6f76e50302ffa900bbd90c7c2db142538b3dfce3fb6fdf8478746d939d

Tx prefix hash: 762e30fed04eb391b64d2b6c70b06a1db6d05ce1881da32dcc01a21f49e9a171
Tx public key: a221050b15e800a5fa04b0d69a7f4f33f0d2aaa9b1c1d45b1f1fc8c55bb1b9df
Timestamp: 1711273217 Timestamp [UCT]: 2024-03-24 09:40:17 Age [y:d:h:m:s]: 01:273:12:55:08
Block: 985228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 454217 RingCT/type: yes/0
Extra: 01a221050b15e800a5fa04b0d69a7f4f33f0d2aaa9b1c1d45b1f1fc8c55bb1b9df02110000001752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e53a4cb31e43bf2390a9b4a70ca30d1ec5239aad6f26c9dcc1510c8ab4af2dad 0.600000000000 1445437 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": 985238, "vin": [ { "gen": { "height": 985228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e53a4cb31e43bf2390a9b4a70ca30d1ec5239aad6f26c9dcc1510c8ab4af2dad" } } ], "extra": [ 1, 162, 33, 5, 11, 21, 232, 0, 165, 250, 4, 176, 214, 154, 127, 79, 51, 240, 210, 170, 169, 177, 193, 212, 91, 31, 31, 200, 197, 91, 177, 185, 223, 2, 17, 0, 0, 0, 23, 82, 212, 126, 148, 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