Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16e047e34fe37694eeb05183dae3c4cf1cf5c72051c7c188ed8d82715dec8f5e

Tx prefix hash: fdca45326a3c9e03e06248e8b8529bde6b350e8f3def1e7b52a77aa837fc78d8
Tx public key: 900cfb48f7bf9b582e15967b30512fdc3b9f130216ae8b4cf2dfaeddb1f46a55
Timestamp: 1675519484 Timestamp [UCT]: 2023-02-04 14:04:44 Age [y:d:h:m:s]: 02:024:06:23:44
Block: 689675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538923 RingCT/type: yes/0
Extra: 01900cfb48f7bf9b582e15967b30512fdc3b9f130216ae8b4cf2dfaeddb1f46a55021100000001faf35c9c000000000000000000

1 output(s) for total of 3.182880663000 dcy

stealth address amount amount idx
00: b065b35d95fdc2d345651c236537d582f9bc0be4efbd380334a2953d27e1c8b0 3.182880663000 1132367 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": 689685, "vin": [ { "gen": { "height": 689675 } } ], "vout": [ { "amount": 3182880663, "target": { "key": "b065b35d95fdc2d345651c236537d582f9bc0be4efbd380334a2953d27e1c8b0" } } ], "extra": [ 1, 144, 12, 251, 72, 247, 191, 155, 88, 46, 21, 150, 123, 48, 81, 47, 220, 59, 159, 19, 2, 22, 174, 139, 76, 242, 223, 174, 221, 177, 244, 106, 85, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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