Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a87c959271971fe3aa79544d9306742345b0807dc73fed75ef2b349ddc0d9204

Tx prefix hash: 4f95b0826f5c57575880b983d62fbe377ab057bfdc0b6eab851e5bb324460aae
Tx public key: 81a0d822a6aefb4a65b07dcdc1b02da2957795279a86e8b34cd0bd8d83862f4e
Timestamp: 1711358651 Timestamp [UCT]: 2024-03-25 09:24:11 Age [y:d:h:m:s]: 00:289:20:24:26
Block: 985943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207456 RingCT/type: yes/0
Extra: 0181a0d822a6aefb4a65b07dcdc1b02da2957795279a86e8b34cd0bd8d83862f4e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a0b3141688b0728bfa51b32b59e79a809c3ff29e537549f9ac6f6946fdd279e 0.600000000000 1446164 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": 985953, "vin": [ { "gen": { "height": 985943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a0b3141688b0728bfa51b32b59e79a809c3ff29e537549f9ac6f6946fdd279e" } } ], "extra": [ 1, 129, 160, 216, 34, 166, 174, 251, 74, 101, 176, 125, 205, 193, 176, 45, 162, 149, 119, 149, 39, 154, 134, 232, 179, 76, 208, 189, 141, 131, 134, 47, 78, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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