← previous blocknext block →recent activity
Analyzing
Block #93,878,874
9 transactions · 8 stateful · 2026-08-07 09:02:15 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,878,874 · 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
1w02w14w05w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0759c8f2…8408
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x9ba6ae4a…90cb
0x34b655…2a6f
4 touches
1 conflict
0x0d227855…8956
0x34b655…2a6f
2 touches
0 conflicts
0x12d581a6…c9e6
0x34b655…2a6f
2 touches
0 conflicts
0x2804845a…c546
0x34b655…2a6f
2 touches
0 conflicts
0x4e58f1d6…2fca
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 0x0759c8f2aa…5b8408
Audit this contract →
← previous block·next block →recent activity