← previous blocknext block →recent activity
Analyzing
Block #93,420,773
19 transactions · 18 stateful · 2026-08-05 18:39:18 UTC
Parallelism
84/100
Blocked
22%
Avg conflicts / tx
0.37
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,420,773 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w07w011w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x064e596a…2275
0x34b655…2a6f
6 touches
3 conflicts
0x8743e1ba…8331
0x34b655…2a6f
6 touches
3 conflicts
0xe00608f8…edc2
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x3293a887…4404
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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
3 conflicts on slot 0x064e596a54…c02275
Audit this contract →
← previous block·next block →recent activity