Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7482c93c60d0bb629cc6704433ac6bd8fd3222cb8e09bafaa4f076c2a54c4bf6

Tx prefix hash: e7ab1bca9815c2739f6614a41db60a26d6f398fdd91274344ca7984a163d6fac
Tx public key: 043acb07f0962bcb51eba8c2fe8bf87acc9d369092629b1cc793c8842503d13a
Timestamp: 1721006498 Timestamp [UCT]: 2024-07-15 01:21:38 Age [y:d:h:m:s]: 00:264:02:21:45
Block: 1065915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188657 RingCT/type: yes/0
Extra: 01043acb07f0962bcb51eba8c2fe8bf87acc9d369092629b1cc793c8842503d13a021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cc923536c4d3b07e9f23f4c4d87b19a212a2b7d96752cee24bc3b6464454a43 0.600000000000 1536484 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": 1065925, "vin": [ { "gen": { "height": 1065915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cc923536c4d3b07e9f23f4c4d87b19a212a2b7d96752cee24bc3b6464454a43" } } ], "extra": [ 1, 4, 58, 203, 7, 240, 150, 43, 203, 81, 235, 168, 194, 254, 139, 248, 122, 204, 157, 54, 144, 146, 98, 155, 28, 199, 147, 200, 132, 37, 3, 209, 58, 2, 17, 0, 0, 0, 1, 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