Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 336a1919a675fb21e8ff36eae226300ce5e01ba6443c22d0dd5ef2d19bc7e44d

Tx prefix hash: 612208b8ba69fc85dbb6e98dc5c70cd8edbe0915195d647bbf14dad398c67114
Tx public key: d316e10c44698c2f55c4ba79e3c1e9ec884832d60ad431a29a05dfb9757a6cb5
Timestamp: 1705535203 Timestamp [UCT]: 2024-01-17 23:46:43 Age [y:d:h:m:s]: 01:300:18:13:17
Block: 937612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473773 RingCT/type: yes/0
Extra: 01d316e10c44698c2f55c4ba79e3c1e9ec884832d60ad431a29a05dfb9757a6cb502110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41d57554fbc87c7985e8aed5b6e5cc5f1419adfbef1623d0486cf85f88cdeb64 0.600000000000 1395674 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": 937622, "vin": [ { "gen": { "height": 937612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41d57554fbc87c7985e8aed5b6e5cc5f1419adfbef1623d0486cf85f88cdeb64" } } ], "extra": [ 1, 211, 22, 225, 12, 68, 105, 140, 47, 85, 196, 186, 121, 227, 193, 233, 236, 136, 72, 50, 214, 10, 212, 49, 162, 154, 5, 223, 185, 117, 122, 108, 181, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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