Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24f2789d6a668eef775d81e711b63a2867771c7764b993db7dcf017d731a82d9

Tx prefix hash: 0cd0a4e10e00a301d4fda5196afaa665811be77d9f9397bbcba68dab8fe3f0b3
Tx public key: f8cb1a9ca2c2c0f857d0c7fe2ab70c9e9d6e44d8f27eb9b84dba3ea4af161729
Timestamp: 1718982203 Timestamp [UCT]: 2024-06-21 15:03:23 Age [y:d:h:m:s]: 00:285:10:35:52
Block: 1049101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203975 RingCT/type: yes/0
Extra: 01f8cb1a9ca2c2c0f857d0c7fe2ab70c9e9d6e44d8f27eb9b84dba3ea4af16172902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6989e607c68b0aa7329567bf2846ad8264f745cc290ef5e5b8dae2df689c540 0.600000000000 1519198 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": 1049111, "vin": [ { "gen": { "height": 1049101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6989e607c68b0aa7329567bf2846ad8264f745cc290ef5e5b8dae2df689c540" } } ], "extra": [ 1, 248, 203, 26, 156, 162, 194, 192, 248, 87, 208, 199, 254, 42, 183, 12, 158, 157, 110, 68, 216, 242, 126, 185, 184, 77, 186, 62, 164, 175, 22, 23, 41, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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