Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8478852e24dd712bf0064e5e9240ece76e1df7dec2ce1e180baf38c24efd3727

Tx prefix hash: 095fa1fc9571c99fb9ac904c0f086e0e80b1e3ce1325db526c3e0b384ca57203
Tx public key: f8f6b6c2bbd9f547357c14de99d9bb3aa9de66ceb7f15a66ca6893aac64bd921
Timestamp: 1705169686 Timestamp [UCT]: 2024-01-13 18:14:46 Age [y:d:h:m:s]: 01:107:05:10:08
Block: 934582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337749 RingCT/type: yes/0
Extra: 01f8f6b6c2bbd9f547357c14de99d9bb3aa9de66ceb7f15a66ca6893aac64bd92102110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f6ad28ea807a690c54244cd03e11651006ffbe11f69920a7d989070463e1c4c 0.600000000000 1392596 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": 934592, "vin": [ { "gen": { "height": 934582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f6ad28ea807a690c54244cd03e11651006ffbe11f69920a7d989070463e1c4c" } } ], "extra": [ 1, 248, 246, 182, 194, 187, 217, 245, 71, 53, 124, 20, 222, 153, 217, 187, 58, 169, 222, 102, 206, 183, 241, 90, 102, 202, 104, 147, 170, 198, 75, 217, 33, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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