← previous blocknext block →recent activity
Analyzing
Block #93,558,216
16 transactions · 16 stateful · 2026-08-06 06:10:14 UTC
Parallelism
81/100
Blocked
19%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,558,216 · 16 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
3w04w18w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd676e291…3ecf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0644aa4a…636f
0x34b655…2a6f
2 touches
0 conflicts
0x0c27b92d…451b
0x34b655…2a6f
2 touches
0 conflicts
0x310afe2c…83e1
0x34b655…2a6f
2 touches
0 conflicts
0x3ad8bbeb…b084
0x34b655…2a6f
2 touches
0 conflicts
0x428b6e5b…8909
0x34b655…2a6f
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 0xd676e29175…2b3ecf
Audit this contract →
← previous block·next block →recent activity