Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bc4cab460473780f47b8fa705543cf02c44c76e4eed8f161aa3737e624bd705

Tx prefix hash: ac4402232d4a76ada636054275cac4d14626cbe8821a86875e4727e99d5d7fb9
Tx public key: e77e4f7060dc90f6f38e2a6ffd8225ec7eb2f31a8d212b7d71ed7dced0d95678
Timestamp: 1734136696 Timestamp [UCT]: 2024-12-14 00:38:16 Age [y:d:h:m:s]: 00:109:01:10:17
Block: 1174660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77702 RingCT/type: yes/0
Extra: 01e77e4f7060dc90f6f38e2a6ffd8225ec7eb2f31a8d212b7d71ed7dced0d956780211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b58b04a8cccca094f2ba0855bd06f1b1b98491ab48ebd0f27bfbe9ab51b87bfa 0.600000000000 1660841 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": 1174670, "vin": [ { "gen": { "height": 1174660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b58b04a8cccca094f2ba0855bd06f1b1b98491ab48ebd0f27bfbe9ab51b87bfa" } } ], "extra": [ 1, 231, 126, 79, 112, 96, 220, 144, 246, 243, 142, 42, 111, 253, 130, 37, 236, 126, 178, 243, 26, 141, 33, 43, 125, 113, 237, 125, 206, 208, 217, 86, 120, 2, 17, 0, 0, 0, 1, 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