← previous blocknext block →recent activity
Analyzing
Block #94,057,987
14 transactions · 14 stateful · 2026-08-08 00:03:32 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,057,987 · 14 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
1w02w14w05w08w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x501b08c7…f471
0x34b655…2a6f
4 touches
1 conflict
0xaf19c45c…d1a8
0x34b655…2a6f
4 touches
1 conflict
0xaf19c45c…d1a9
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xcfb812b8…26e0
0x065c9d…c394
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
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 0x501b08c77e…c9f471
Audit this contract →
← previous block·next block →recent activity