← previous blocknext block →recent activity
Analyzing
Block #93,490,384
8 transactions · 7 stateful · 2026-08-06 00:29:14 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,490,384 · 8 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
1w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0x3a5cd535…3546
0x34b655…2a6f
2 touches
0 conflicts
0x46cd4b95…4fe1
0x34b655…2a6f
2 touches
0 conflicts
0x7a5b43f9…1ba3
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4a2
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4a3
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 0x9b2d3bee9d…d68eec
Audit this contract →
← previous block·next block →recent activity