← previous blocknext block →recent activity
Analyzing
Block #94,132,951
16 transactions · 15 stateful · 2026-08-08 06:21:15 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,132,951 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w08w09w110w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8252706a…7ca5
0x34b655…2a6f
8 touches
6 conflicts
0xda12e7f3…e890
0x34b655…2a6f
6 touches
3 conflicts
0xea2d949b…9b29
0x34b655…2a6f
6 touches
3 conflicts
0x314add6a…c880
0x34b655…2a6f
4 touches
1 conflict
0x349f436e…80e6
0x34b655…2a6f
4 touches
1 conflict
0x41c66186…229a
0x34b655…2a6f
4 touches
1 conflict
0x60520483…e2ef
0x34b655…2a6f
4 touches
1 conflict
0x62738158…e746
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
6 conflicts on slot 0x8252706a8a…797ca5
Audit this contract →
← previous block·next block →recent activity