Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e7f931022908d00d3aba128b7eb6f3338bc1615c97f6474f8055090c38bdbbc

Tx prefix hash: bf4358ce5ef6603d7d80dad524f0edd38befeb2042aaf488ee0dff4f254021d3
Tx public key: e0b9e6dfb9912eb61e446732f63b73f379ace831499af8238af3b964e942ad5b
Timestamp: 1608478191 Timestamp [UCT]: 2020-12-20 15:29:51 Age [y:d:h:m:s]: 04:007:17:31:16
Block: 165868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1018316 RingCT/type: yes/0
Extra: 01e0b9e6dfb9912eb61e446732f63b73f379ace831499af8238af3b964e942ad5b02110000009a27e2517e000000000000000000

1 output(s) for total of 173.154449664000 dcy

stealth address amount amount idx
00: 3b8005dfdf91c43752ee8059b47eedbb32fbebc5c73bfa6e1f3372c7b91d7993 173.154449664000 302593 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": 165878, "vin": [ { "gen": { "height": 165868 } } ], "vout": [ { "amount": 173154449664, "target": { "key": "3b8005dfdf91c43752ee8059b47eedbb32fbebc5c73bfa6e1f3372c7b91d7993" } } ], "extra": [ 1, 224, 185, 230, 223, 185, 145, 46, 182, 30, 68, 103, 50, 246, 59, 115, 243, 121, 172, 232, 49, 73, 154, 248, 35, 138, 243, 185, 100, 233, 66, 173, 91, 2, 17, 0, 0, 0, 154, 39, 226, 81, 126, 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