Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bb8b889cb1ede51e9f88b15d11d8827e4fc06022bb9f0e06c3339f906c926a0

Tx prefix hash: 1d15a01306928e9583a127eda35511fe86b69f790009ecd2cf8100f565513f51
Tx public key: 3d69cc4e8b20cbbb099c48b672f8a84702b1323d60f7d7d2308bca16c037398c
Timestamp: 1718327311 Timestamp [UCT]: 2024-06-14 01:08:31 Age [y:d:h:m:s]: 01:149:12:55:59
Block: 1043689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365437 RingCT/type: yes/0
Extra: 013d69cc4e8b20cbbb099c48b672f8a84702b1323d60f7d7d2308bca16c037398c0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fb0f08b0313439f0b1ec75ef6a946969787154abc3310eeaca5c36f3fc27829 0.600000000000 1512846 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": 1043699, "vin": [ { "gen": { "height": 1043689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fb0f08b0313439f0b1ec75ef6a946969787154abc3310eeaca5c36f3fc27829" } } ], "extra": [ 1, 61, 105, 204, 78, 139, 32, 203, 187, 9, 156, 72, 182, 114, 248, 168, 71, 2, 177, 50, 61, 96, 247, 215, 210, 48, 139, 202, 22, 192, 55, 57, 140, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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