Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf6253971e711fc6a8197bf5a748c30ab9a1d164dba6ca0e350327acb00383b8

Tx prefix hash: 60320a86970de483d9f3c7a0cee846ec173f753ffc9ee020e9d898d354fa0435
Tx public key: 6b93f3f30e673032ede6bf4ad407045d0c56ba91f17976fdc7f0f8d41712150d
Timestamp: 1728065083 Timestamp [UCT]: 2024-10-04 18:04:43 Age [y:d:h:m:s]: 01:037:09:13:39
Block: 1124429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285095 RingCT/type: yes/0
Extra: 016b93f3f30e673032ede6bf4ad407045d0c56ba91f17976fdc7f0f8d41712150d02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89e0a0efeaea51d4a27954f48ed2505fc910530d782e58375af5f2a6d681012d 0.600000000000 1607048 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": 1124439, "vin": [ { "gen": { "height": 1124429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89e0a0efeaea51d4a27954f48ed2505fc910530d782e58375af5f2a6d681012d" } } ], "extra": [ 1, 107, 147, 243, 243, 14, 103, 48, 50, 237, 230, 191, 74, 212, 7, 4, 93, 12, 86, 186, 145, 241, 121, 118, 253, 199, 240, 248, 212, 23, 18, 21, 13, 2, 17, 0, 0, 0, 1, 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