← previous blocknext block →recent activity
Analyzing
Block #94,199,231
9 transactions · 6 stateful · 2026-08-08 11:57:12 UTC
Parallelism
78/100
Blocked
17%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,199,231 · 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d4a544d…41f3
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x784eaad2…d176
0x34b655…2a6f
4 touches
1 conflict
0x784eaad2…d177
0x34b655…2a6f
4 touches
1 conflict
0x86447c2b…7785
0x34b655…2a6f
3 touches
1 conflict
0x7167d534…b8f4
0x34b655…2a6f
3 touches
1 conflict
0x3df0422c…fd38
0x34b655…2a6f
2 touches
0 conflicts
0x3df0422c…fd39
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 0x5d4a544da3…e941f3
Audit this contract →
← previous block·next block →recent activity