Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8dc5cf3a6f9bbd079848d772902c82703b559303f7d86d8b5cc55d75f86c782

Tx prefix hash: 70de30e9e12925fe56ccc9ca3829de3740a3a4f954caa94fd85f4966dc89e73a
Tx public key: 1075663c7ae0759bbc0fdfbed35e6e25f727e58607c6843515c6522ac321a49a
Timestamp: 1717265911 Timestamp [UCT]: 2024-06-01 18:18:31 Age [y:d:h:m:s]: 00:239:22:40:32
Block: 1034897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171470 RingCT/type: yes/0
Extra: 011075663c7ae0759bbc0fdfbed35e6e25f727e58607c6843515c6522ac321a49a021100000005e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46d253ce90e4b58c0fe59a84297554e24a3b46976df2431de0c5cc25efde116e 0.600000000000 1503416 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": 1034907, "vin": [ { "gen": { "height": 1034897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46d253ce90e4b58c0fe59a84297554e24a3b46976df2431de0c5cc25efde116e" } } ], "extra": [ 1, 16, 117, 102, 60, 122, 224, 117, 155, 188, 15, 223, 190, 211, 94, 110, 37, 247, 39, 229, 134, 7, 198, 132, 53, 21, 198, 82, 42, 195, 33, 164, 154, 2, 17, 0, 0, 0, 5, 224, 133, 50, 182, 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