← previous blocknext block →recent activity
Analyzing
Block #94,276,245
10 transactions · 8 stateful · 2026-08-08 18:27:38 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,276,245 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a57a2b8…3cdd
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x78d3c586…34b2
0xa6afd3…d132
4 touches
1 conflict
0x2a9e9bd1…5368
0x2a68ba…90c5
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0xeece21b9…1fa2
0x065c9d…c394
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 0x0a57a2b8cd…773cdd
Audit this contract →
← previous block·next block →recent activity