← previous blocknext block →recent activity
Analyzing
Block #93,186,288
9 transactions · 8 stateful · 2026-08-04 23:00:21 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,186,288 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7aae9795…06ed
0x34b655…2a6f
6 touches
3 conflicts
0x37d710c8…45c1
0x34b655…2a6f
4 touches
1 conflict
0x84ee6168…3f13
0x34b655…2a6f
4 touches
1 conflict
0x3d158563…8713
0x34b655…2a6f
4 touches
1 conflict
0x19002825…07e6
0x34b655…2a6f
3 touches
1 conflict
0x22d93518…26d1
0x34b655…2a6f
2 touches
0 conflicts
0x3a3b955d…e6fd
0x34b655…2a6f
2 touches
0 conflicts
0x5d7f3048…8897
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
3 conflicts on slot 0x7aae979517…b606ed
Audit this contract →
← previous block·next block →recent activity