Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a4fa972801c53f3bbed7e68a9cc315af523e98415e72975af3badbbd74d6008

Tx prefix hash: 71b4e99a8134a317b18a2f5a5454b8252274d3b89562a8891c4a3a32ab7cafc3
Tx public key: 970cdfa4bb14648b61b526e76e6731c107465a93ccea55d4d26ba699e9f426b2
Timestamp: 1722932862 Timestamp [UCT]: 2024-08-06 08:27:42 Age [y:d:h:m:s]: 00:316:04:02:17
Block: 1081865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225792 RingCT/type: yes/0
Extra: 01970cdfa4bb14648b61b526e76e6731c107465a93ccea55d4d26ba699e9f426b2021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6e62d17100b76981fc54255b1cb30aa12b5135a4f486541aa11e24e2a1c38e7 0.600000000000 1555688 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": 1081875, "vin": [ { "gen": { "height": 1081865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6e62d17100b76981fc54255b1cb30aa12b5135a4f486541aa11e24e2a1c38e7" } } ], "extra": [ 1, 151, 12, 223, 164, 187, 20, 100, 139, 97, 181, 38, 231, 110, 103, 49, 193, 7, 70, 90, 147, 204, 234, 85, 212, 210, 107, 166, 153, 233, 244, 38, 178, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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