Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 097290cdf1109e610dc3555eba7e542472a00ecd19a0978bf1a9a87c128e22df

Tx prefix hash: 49f7fd7eeda1e59fb974fd2787c7ca35804c227a4f4b98523041bd363bc036ae
Tx public key: ee8246a72cd563efcb6a8c7d5589397fbdfab96b07696426b959052518e5531e
Timestamp: 1736845262 Timestamp [UCT]: 2025-01-14 09:01:02 Age [y:d:h:m:s]: 00:155:01:32:56
Block: 1197067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110523 RingCT/type: yes/0
Extra: 01ee8246a72cd563efcb6a8c7d5589397fbdfab96b07696426b959052518e5531e0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10fb18e10d77b50751c7d58a1caf31e9c3d2ae3ed4e55eb333b8cfd804499a4d 0.600000000000 1683672 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": 1197077, "vin": [ { "gen": { "height": 1197067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10fb18e10d77b50751c7d58a1caf31e9c3d2ae3ed4e55eb333b8cfd804499a4d" } } ], "extra": [ 1, 238, 130, 70, 167, 44, 213, 99, 239, 203, 106, 140, 125, 85, 137, 57, 127, 189, 250, 185, 107, 7, 105, 100, 38, 185, 89, 5, 37, 24, 229, 83, 30, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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