Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0468aaf44ad5e664e5e08f4f64dea19f16067245a6a9b89f50004f3b72eb3956

Tx prefix hash: f120f801d5dbf875395034886bc7d20a79f15ad08b0bb82fde3bffbfccd75d74
Tx public key: 05bd4d366e24d911b0e448e99a6b25e39aafa5982b0f850c6f731ed59f42f766
Timestamp: 1726575142 Timestamp [UCT]: 2024-09-17 12:12:22 Age [y:d:h:m:s]: 00:250:00:35:03
Block: 1112064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178563 RingCT/type: yes/0
Extra: 0105bd4d366e24d911b0e448e99a6b25e39aafa5982b0f850c6f731ed59f42f766021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 133f7b3b20948dc28cc1bc2039ff961cb37706825f4a7a2178648a15a4c0909d 0.600000000000 1591253 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": 1112074, "vin": [ { "gen": { "height": 1112064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "133f7b3b20948dc28cc1bc2039ff961cb37706825f4a7a2178648a15a4c0909d" } } ], "extra": [ 1, 5, 189, 77, 54, 110, 36, 217, 17, 176, 228, 72, 233, 154, 107, 37, 227, 154, 175, 165, 152, 43, 15, 133, 12, 111, 115, 30, 213, 159, 66, 247, 102, 2, 17, 0, 0, 0, 3, 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