Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d486dc511c5e1693cc4f7c15ac8985edcc9ce7e136f86159583dca4896992a37

Tx prefix hash: 6192e722f90bfeba533483c2ef8a9fd82b9b3d4d9370f9e5fd156e64952c4ae2
Tx public key: a46be0dc67e4a7874bad83e59c0dd7da53840e0128351737ed1a32c5def54bbd
Timestamp: 1718210635 Timestamp [UCT]: 2024-06-12 16:43:55 Age [y:d:h:m:s]: 00:277:18:28:31
Block: 1042721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198513 RingCT/type: yes/0
Extra: 01a46be0dc67e4a7874bad83e59c0dd7da53840e0128351737ed1a32c5def54bbd02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90db4be78009683d9ba716ff10aa0c3af45a10bdd5d3ce313e58d8ec21abbd0c 0.600000000000 1511708 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": 1042731, "vin": [ { "gen": { "height": 1042721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90db4be78009683d9ba716ff10aa0c3af45a10bdd5d3ce313e58d8ec21abbd0c" } } ], "extra": [ 1, 164, 107, 224, 220, 103, 228, 167, 135, 75, 173, 131, 229, 156, 13, 215, 218, 83, 132, 14, 1, 40, 53, 23, 55, 237, 26, 50, 197, 222, 245, 75, 189, 2, 17, 0, 0, 0, 3, 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