Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3544800ae7f72d206f11a91c6e3cb1faf560ccd192bfce632421caeb0d15544e

Tx prefix hash: bdeb9750ece951f65b1c02f2cece7d05e57b60d5c0ced6e165cc7b034a825f2b
Tx public key: 141d1a98550f0426860bff2ff86f0a97c52559b704e5c5e48353d7368ca10d4a
Timestamp: 1709216689 Timestamp [UCT]: 2024-02-29 14:24:49 Age [y:d:h:m:s]: 00:361:12:06:06
Block: 968162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258464 RingCT/type: yes/0
Extra: 01141d1a98550f0426860bff2ff86f0a97c52559b704e5c5e48353d7368ca10d4a0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10fe725d392986dbb442b415d0eefeb2145d83260e850a4b90a0b9beea4a1b38 0.600000000000 1427963 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": 968172, "vin": [ { "gen": { "height": 968162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10fe725d392986dbb442b415d0eefeb2145d83260e850a4b90a0b9beea4a1b38" } } ], "extra": [ 1, 20, 29, 26, 152, 85, 15, 4, 38, 134, 11, 255, 47, 248, 111, 10, 151, 197, 37, 89, 183, 4, 229, 197, 228, 131, 83, 215, 54, 140, 161, 13, 74, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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