Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d043e463d11f0291fdbfdea3e316f8a8429d6875be340f154e8dda2c1077214

Tx prefix hash: bf733507b9048f5f654aa5f57e62a4f87f4d0be6d73e7822c51400abb479ad9d
Tx public key: bd2825701f347348c1f4363d0a9468dcf14a44987e4f717f7fc649d259e3d110
Timestamp: 1736227772 Timestamp [UCT]: 2025-01-07 05:29:32 Age [y:d:h:m:s]: 00:162:13:00:56
Block: 1191958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115867 RingCT/type: yes/0
Extra: 01bd2825701f347348c1f4363d0a9468dcf14a44987e4f717f7fc649d259e3d1100211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb442019fdaafb2b3c6228d9b9a0f483628e33123a1fe08f13c003c0a1dbc129 0.600000000000 1678503 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": 1191968, "vin": [ { "gen": { "height": 1191958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb442019fdaafb2b3c6228d9b9a0f483628e33123a1fe08f13c003c0a1dbc129" } } ], "extra": [ 1, 189, 40, 37, 112, 31, 52, 115, 72, 193, 244, 54, 61, 10, 148, 104, 220, 241, 74, 68, 152, 126, 79, 113, 127, 127, 198, 73, 210, 89, 227, 209, 16, 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