Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 206d097331946ccc3a1b6647eeecf1311a13c4ba1281f09fc9134b2502a98e00

Tx prefix hash: 7af9f0b1e5a1d270793245364f0db45c0b5cbe341ac2ff382387d3b8a0b85ce2
Tx public key: f56771b32ffa1f3dbe6d6e46b5ff7707ce03b742d022c8cf32a123803979e9ca
Timestamp: 1736558975 Timestamp [UCT]: 2025-01-11 01:29:35 Age [y:d:h:m:s]: 00:071:17:37:39
Block: 1194690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51047 RingCT/type: yes/0
Extra: 01f56771b32ffa1f3dbe6d6e46b5ff7707ce03b742d022c8cf32a123803979e9ca0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4fc7ecce7dca05d4caf6dc3ad47612dca83849533a0881cbc12b3af0a041f38 0.600000000000 1681267 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": 1194700, "vin": [ { "gen": { "height": 1194690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4fc7ecce7dca05d4caf6dc3ad47612dca83849533a0881cbc12b3af0a041f38" } } ], "extra": [ 1, 245, 103, 113, 179, 47, 250, 31, 61, 190, 109, 110, 70, 181, 255, 119, 7, 206, 3, 183, 66, 208, 34, 200, 207, 50, 161, 35, 128, 57, 121, 233, 202, 2, 17, 0, 0, 0, 6, 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