← previous blocknext block →recent activity
Analyzing
Block #93,149,820
9 transactions · 9 stateful · 2026-08-04 19:56:59 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,149,820 · 9 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
1w02w13w04w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a746750…e0fb
0x34b655…2a6f
4 touches
1 conflict
0x772ab420…c2f6
0x34b655…2a6f
4 touches
1 conflict
0x6713b018…05f3
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xcad6e6d3…cf9f
0x34b655…2a6f
4 touches
1 conflict
0xd2e196a2…20c3
0x34b655…2a6f
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
1 conflict on slot 0x5a746750ba…a5e0fb
Audit this contract →
← previous block·next block →recent activity