Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 876b64b6d737f08e3cc1d4ca46188d4ae6ae1936cb6670e81a28bc53963f63a5

Tx prefix hash: 79e40fc5777cc1fea2e335a38fd5ee3b370472ca9adc07d7a301b568a6ba449d
Tx public key: 5f9fa53ccfe7865b1d98514d18d71a0f5bf749a5411d9a37b961ad43c650bc5c
Timestamp: 1726840774 Timestamp [UCT]: 2024-09-20 13:59:34 Age [y:d:h:m:s]: 00:196:09:56:26
Block: 1114265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140200 RingCT/type: yes/0
Extra: 015f9fa53ccfe7865b1d98514d18d71a0f5bf749a5411d9a37b961ad43c650bc5c021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c2f86abc503b3b0e4a1073999d150623441fb13110fc1a48e629cb7377ecedd 0.600000000000 1594064 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": 1114275, "vin": [ { "gen": { "height": 1114265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c2f86abc503b3b0e4a1073999d150623441fb13110fc1a48e629cb7377ecedd" } } ], "extra": [ 1, 95, 159, 165, 60, 207, 231, 134, 91, 29, 152, 81, 77, 24, 215, 26, 15, 91, 247, 73, 165, 65, 29, 154, 55, 185, 97, 173, 67, 198, 80, 188, 92, 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