← previous blocknext block →recent activity
Analyzing
Block #94,234,511
8 transactions · 7 stateful · 2026-08-08 14:56:00 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,234,511 · 8 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
1w02w03w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64ac7e40…5d7d
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x6ba5204d…3fa6
0x34b655…2a6f
4 touches
1 conflict
0x320701d5…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x320701d5…f9f4
0x34b655…2a6f
4 touches
1 conflict
0x95c47f03…f1bb
0x34b655…2a6f
4 touches
1 conflict
0xd5c59987…b209
0x34b655…2a6f
4 touches
1 conflict
0x5a0a2b03…ac50
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 0x64ac7e4028…765d7d
Audit this contract →
← previous block·next block →recent activity