Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c2df10bc8975f6724ade31aee3c8cf5505adf7bf76a804e1a98bef449efd7ac

Tx prefix hash: 81a3e960b70cc7a4ae8e6d25de1c92ebf34a065cb9001041524cd81d0096d6f0
Tx public key: a59592a2cb071918657dbb06c12564bbf78dc3e7712f38b3c813c267b60bc63e
Timestamp: 1706909937 Timestamp [UCT]: 2024-02-02 21:38:57 Age [y:d:h:m:s]: 01:134:21:06:16
Block: 949016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357409 RingCT/type: yes/0
Extra: 01a59592a2cb071918657dbb06c12564bbf78dc3e7712f38b3c813c267b60bc63e0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a9aa6e23779bf22cb15af299e5c86c63a4ac9c39ebd16a745bd8cd69c443afd 0.600000000000 1407538 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": 949026, "vin": [ { "gen": { "height": 949016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a9aa6e23779bf22cb15af299e5c86c63a4ac9c39ebd16a745bd8cd69c443afd" } } ], "extra": [ 1, 165, 149, 146, 162, 203, 7, 25, 24, 101, 125, 187, 6, 193, 37, 100, 187, 247, 141, 195, 231, 113, 47, 56, 179, 200, 19, 194, 103, 182, 11, 198, 62, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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