← previous blocknext block →recent activity
Analyzing
Block #93,751,860
10 transactions · 8 stateful · 2026-08-06 22:23:43 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,751,860 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fde4971…aac9
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xfd42a6b9…4c81
0x34b655…2a6f
4 touches
1 conflict
0x88b1d110…aca0
0xd32edf…ff58
3 touches
1 conflict
0xc674f667…01d4
0x065c9d…c394
2 touches
0 conflicts
0xc692ea8b…584b
0x065c9d…c394
2 touches
0 conflicts
0xdcb7e376…2e90
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0x5fde497131…e8aac9
Audit this contract →
← previous block·next block →recent activity