Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24f5676e3d87150ae863e22258b045afd41f00afac6f9e70f7d9e8a0cf9f5b30

Tx prefix hash: 43565f400a2eead9d6c1e8e4b6ac0203059a068829697e8b216460f006623178
Tx public key: a8aab22f6fb7abf6075452066d417ad5ed03eb0299992905a0a751df12a213b5
Timestamp: 1730519333 Timestamp [UCT]: 2024-11-02 03:48:53 Age [y:d:h:m:s]: 00:135:09:00:05
Block: 1144682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96600 RingCT/type: yes/0
Extra: 01a8aab22f6fb7abf6075452066d417ad5ed03eb0299992905a0a751df12a213b50211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 098584739036a77c9f4caa99671921692ea7dd4e8f29d757b52deea5420eac7e 0.600000000000 1628961 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": 1144692, "vin": [ { "gen": { "height": 1144682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "098584739036a77c9f4caa99671921692ea7dd4e8f29d757b52deea5420eac7e" } } ], "extra": [ 1, 168, 170, 178, 47, 111, 183, 171, 246, 7, 84, 82, 6, 109, 65, 122, 213, 237, 3, 235, 2, 153, 153, 41, 5, 160, 167, 81, 223, 18, 162, 19, 181, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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