Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31f285b7e69b7af6770e537a5ec7fb32654436d6aa0da90b400780ba7830dd3f

Tx prefix hash: 111dd0e21335937352a26036c2dea2630b9b1f085098cac4bab7c3e9bcd4a889
Tx public key: bb3051c0f38efc6852c9c27234aa97042559c3a9ae01573a20d65b71eaafa4c7
Timestamp: 1723854449 Timestamp [UCT]: 2024-08-17 00:27:29 Age [y:d:h:m:s]: 00:234:18:03:43
Block: 1089518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167640 RingCT/type: yes/0
Extra: 01bb3051c0f38efc6852c9c27234aa97042559c3a9ae01573a20d65b71eaafa4c7021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69572d09b01cd44d3d3c8a631b2a38290030ef4648ac388f48d6464c1858aa71 0.600000000000 1564139 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": 1089528, "vin": [ { "gen": { "height": 1089518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69572d09b01cd44d3d3c8a631b2a38290030ef4648ac388f48d6464c1858aa71" } } ], "extra": [ 1, 187, 48, 81, 192, 243, 142, 252, 104, 82, 201, 194, 114, 52, 170, 151, 4, 37, 89, 195, 169, 174, 1, 87, 58, 32, 214, 91, 113, 234, 175, 164, 199, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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