Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d8e7023aac5d760e5e5318a6b82c33ce388be6395aa76917fadad14d86f3872

Tx prefix hash: b041b7501f1a7f24c3cef25ada36aa411b71fdaf0f3007559a900acbdb5c2ee6
Tx public key: d1d20d198427f4f8b739992ac0502e4b04e4af07cf477a51cbdd9ce2b7d63827
Timestamp: 1710749549 Timestamp [UCT]: 2024-03-18 08:12:29 Age [y:d:h:m:s]: 01:027:16:08:51
Block: 980890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280732 RingCT/type: yes/0
Extra: 01d1d20d198427f4f8b739992ac0502e4b04e4af07cf477a51cbdd9ce2b7d6382702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 411f7e72999b68b2079d3c109ddd3ceb0ddf9ab7a789c86e8a66a488de981c41 0.600000000000 1440975 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": 980900, "vin": [ { "gen": { "height": 980890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "411f7e72999b68b2079d3c109ddd3ceb0ddf9ab7a789c86e8a66a488de981c41" } } ], "extra": [ 1, 209, 210, 13, 25, 132, 39, 244, 248, 183, 57, 153, 42, 192, 80, 46, 75, 4, 228, 175, 7, 207, 71, 122, 81, 203, 221, 156, 226, 183, 214, 56, 39, 2, 17, 0, 0, 0, 1, 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