Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c986073c61864a074eafd4b28dd76956ec70b4158c62d6648aa8cfcc3f9c901c

Tx prefix hash: 56b0588a1e076e0355788bf3898072b7410965682396a1a6c8a4c05ba962677c
Tx public key: a817f1b28d7f793840cf78c6b3847f390f88eae06614fa77069df88b443c6913
Timestamp: 1708699543 Timestamp [UCT]: 2024-02-23 14:45:43 Age [y:d:h:m:s]: 01:114:20:27:50
Block: 963868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343051 RingCT/type: yes/0
Extra: 01a817f1b28d7f793840cf78c6b3847f390f88eae06614fa77069df88b443c691302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c013d6d329d812997074d1716a4f5cb9a9717cf24250d66155ae82a404d1346a 0.600000000000 1423595 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": 963878, "vin": [ { "gen": { "height": 963868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c013d6d329d812997074d1716a4f5cb9a9717cf24250d66155ae82a404d1346a" } } ], "extra": [ 1, 168, 23, 241, 178, 141, 127, 121, 56, 64, 207, 120, 198, 179, 132, 127, 57, 15, 136, 234, 224, 102, 20, 250, 119, 6, 157, 248, 139, 68, 60, 105, 19, 2, 17, 0, 0, 0, 2, 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