Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71aee1c4477e2f9bce08571285c30bb768de78e050f19860481d8c076e7c1d5d

Tx prefix hash: 6d9dfadd983b3e6061773bc47a4ee1bc1639ee8cb8b4a83e28cca1df806c8d0c
Tx public key: a24679774161aab8609986e36855cb44e5c0dba0573f3ae3a0ff73fef53be275
Timestamp: 1712574764 Timestamp [UCT]: 2024-04-08 11:12:44 Age [y:d:h:m:s]: 00:221:00:13:32
Block: 995968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158245 RingCT/type: yes/0
Extra: 01a24679774161aab8609986e36855cb44e5c0dba0573f3ae3a0ff73fef53be27502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62dc4544f5fff31fc144f730b8055c5b744e9f8428caf57e2d3e8d1f851c91a1 0.600000000000 1456384 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": 995978, "vin": [ { "gen": { "height": 995968 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62dc4544f5fff31fc144f730b8055c5b744e9f8428caf57e2d3e8d1f851c91a1" } } ], "extra": [ 1, 162, 70, 121, 119, 65, 97, 170, 184, 96, 153, 134, 227, 104, 85, 203, 68, 229, 192, 219, 160, 87, 63, 58, 227, 160, 255, 115, 254, 245, 59, 226, 117, 2, 17, 0, 0, 0, 1, 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