Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7688f318c73ec17a6df3b0b47eefafe99c04573aa1ee0dea963ae9b3cda83ab

Tx prefix hash: 22dad209d9c7cf391739a911f1394c3e0911278dfc026d5ba93fde6a3177c099
Tx public key: c2e0cff9c7ec3719798a4265e01bf2c033341dfed8499f2f72b64eefb8cc1e5c
Timestamp: 1741192094 Timestamp [UCT]: 2025-03-05 16:28:14 Age [y:d:h:m:s]: 00:007:01:24:49
Block: 1232791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5059 RingCT/type: yes/0
Extra: 01c2e0cff9c7ec3719798a4265e01bf2c033341dfed8499f2f72b64eefb8cc1e5c021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8600806be363e41cfeb54f3fcc7d831ceaf3da53e5cf538c55063e7bccf220a6 0.600000000000 1719706 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": 1232801, "vin": [ { "gen": { "height": 1232791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8600806be363e41cfeb54f3fcc7d831ceaf3da53e5cf538c55063e7bccf220a6" } } ], "extra": [ 1, 194, 224, 207, 249, 199, 236, 55, 25, 121, 138, 66, 101, 224, 27, 242, 192, 51, 52, 29, 254, 216, 73, 159, 47, 114, 182, 78, 239, 184, 204, 30, 92, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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