Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af2e0764ca6397dcfd5c7f61197c3434dd958319768550a7d3960c71a95e4c03

Tx prefix hash: 49140372425643f7e47bf694dc729445c26df234742bffac804d703d09220a49
Tx public key: 74b341ae06c4f2daad0f46b980f7e10a875ad9269ee84f6fdc495ccd6bb8a248
Timestamp: 1736772150 Timestamp [UCT]: 2025-01-13 12:42:30 Age [y:d:h:m:s]: 00:156:11:11:41
Block: 1196459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111517 RingCT/type: yes/0
Extra: 0174b341ae06c4f2daad0f46b980f7e10a875ad9269ee84f6fdc495ccd6bb8a2480211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 223bb6256a6f3d0011f44846d6980f1103ff1ec15ab83b049ae1d443d620e83b 0.600000000000 1683058 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": 1196469, "vin": [ { "gen": { "height": 1196459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "223bb6256a6f3d0011f44846d6980f1103ff1ec15ab83b049ae1d443d620e83b" } } ], "extra": [ 1, 116, 179, 65, 174, 6, 196, 242, 218, 173, 15, 70, 185, 128, 247, 225, 10, 135, 90, 217, 38, 158, 232, 79, 111, 220, 73, 92, 205, 107, 184, 162, 72, 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