Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ad250a6a043af1e40ebfb8e42e687b1fa5ccb3b37cb423759d6da834c8c69f0

Tx prefix hash: 81fbada5b561e54b1523eca16d52bdf622e9c1a707588fee80718c9cbf9c182f
Tx public key: ab0035f56519f7e10f0572f7a3bb646838cf5e89a03e886c7ee3a82dec01876b
Timestamp: 1674330173 Timestamp [UCT]: 2023-01-21 19:42:53 Age [y:d:h:m:s]: 02:093:06:04:05
Block: 679800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 588301 RingCT/type: yes/0
Extra: 01ab0035f56519f7e10f0572f7a3bb646838cf5e89a03e886c7ee3a82dec01876b021100000001e6d27f9c000000000000000000

1 output(s) for total of 3.431945199000 dcy

stealth address amount amount idx
00: 357ebfbb97b50604251a48db1a1c91c913304bd6112f9440f3c02d2c619d7f24 3.431945199000 1121811 of 0

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": 679810, "vin": [ { "gen": { "height": 679800 } } ], "vout": [ { "amount": 3431945199, "target": { "key": "357ebfbb97b50604251a48db1a1c91c913304bd6112f9440f3c02d2c619d7f24" } } ], "extra": [ 1, 171, 0, 53, 245, 101, 25, 247, 225, 15, 5, 114, 247, 163, 187, 100, 104, 56, 207, 94, 137, 160, 62, 136, 108, 126, 227, 168, 45, 236, 1, 135, 107, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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