← previous blocknext block →recent activity
Analyzing
Block #94,200,161
18 transactions · 17 stateful · 2026-08-08 12:01:53 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.61
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,200,161 · 18 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
1w02w03w04w15w06w18w110w011w112w213w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x058d5849…bbd6
0x34b655…2a6f
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x74f95963…01a2
0x34b655…2a6f
6 touches
3 conflicts
0xbbc4a563…d531
0x065c9d…c394
6 touches
3 conflicts
0xbca4de0c…577c
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
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
3 conflicts on slot 0x058d584958…56bbd6
Audit this contract →
← previous block·next block →recent activity