Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56b06fff024d50d68b7af319d596b80f76f27fb0da554e93c53ea6740095dd7f

Tx prefix hash: c537ff598558094075cfd196f9b85be1306b7f0a22acf3c044ff9317e42c0d55
Tx public key: 7ca879a719aac4514ccf6fba40b34d75646e33a1ca69a893b23c40ed013a8e30
Timestamp: 1715345678 Timestamp [UCT]: 2024-05-10 12:54:38 Age [y:d:h:m:s]: 00:294:10:02:21
Block: 1018975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210413 RingCT/type: yes/0
Extra: 017ca879a719aac4514ccf6fba40b34d75646e33a1ca69a893b23c40ed013a8e3002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06e4da1ec91a2104cfb18a336c52d9726301e881b4d2fd137566ab6c238a7582 0.600000000000 1482812 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": 1018985, "vin": [ { "gen": { "height": 1018975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06e4da1ec91a2104cfb18a336c52d9726301e881b4d2fd137566ab6c238a7582" } } ], "extra": [ 1, 124, 168, 121, 167, 25, 170, 196, 81, 76, 207, 111, 186, 64, 179, 77, 117, 100, 110, 51, 161, 202, 105, 168, 147, 178, 60, 64, 237, 1, 58, 142, 48, 2, 17, 0, 0, 0, 3, 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