Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4b08b7c6c95c1e9600461ad74e685dcb11bc6617980cd742eafcdd262e8b8b6

Tx prefix hash: 9a382c4dd264b64f45c43715f5e5d0d77c12648a6e063810e89ba7d7beddb192
Tx public key: af5cfa02897eb1e4f727614c1e34e5183f61e35e8f3b256ab9d409829b52196f
Timestamp: 1689556732 Timestamp [UCT]: 2023-07-17 01:18:52 Age [y:d:h:m:s]: 01:329:20:16:14
Block: 805426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496900 RingCT/type: yes/0
Extra: 01af5cfa02897eb1e4f727614c1e34e5183f61e35e8f3b256ab9d409829b52196f02110000000875e3f0e9000000000000000000

1 output(s) for total of 1.316101656000 dcy

stealth address amount amount idx
00: 7b8d6c47d4462e722cb91b99f48378cdb314a5ed1b077e8712a740058a34b326 1.316101656000 1256653 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": 805436, "vin": [ { "gen": { "height": 805426 } } ], "vout": [ { "amount": 1316101656, "target": { "key": "7b8d6c47d4462e722cb91b99f48378cdb314a5ed1b077e8712a740058a34b326" } } ], "extra": [ 1, 175, 92, 250, 2, 137, 126, 177, 228, 247, 39, 97, 76, 30, 52, 229, 24, 63, 97, 227, 94, 143, 59, 37, 106, 185, 212, 9, 130, 155, 82, 25, 111, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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