Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d89667fd64df48d1cb4ce7b7a00ccf9988c470fcef191cb58cf2f2a0e53ab9a4

Tx prefix hash: 2898ddd027416ae14eb6f9e260bbaf333f70bbc3b4b98f3f012a50b95f76c534
Tx public key: bdf9e9ad536e137dfc2e8c3a0f485fe43cc730c1fad51d90e75ee322e8ee89f9
Timestamp: 1721309797 Timestamp [UCT]: 2024-07-18 13:36:37 Age [y:d:h:m:s]: 00:246:15:04:53
Block: 1068438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176158 RingCT/type: yes/0
Extra: 01bdf9e9ad536e137dfc2e8c3a0f485fe43cc730c1fad51d90e75ee322e8ee89f902110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f11c5dffea6dd1bbebc43d86a31ecde0596981d7d7a604aae0b59f63bada0ac 0.600000000000 1539515 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": 1068448, "vin": [ { "gen": { "height": 1068438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f11c5dffea6dd1bbebc43d86a31ecde0596981d7d7a604aae0b59f63bada0ac" } } ], "extra": [ 1, 189, 249, 233, 173, 83, 110, 19, 125, 252, 46, 140, 58, 15, 72, 95, 228, 60, 199, 48, 193, 250, 213, 29, 144, 231, 94, 227, 34, 232, 238, 137, 249, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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