← previous blocknext block →recent activity
Analyzing
Block #94,487,069
8 transactions · 8 stateful · 2026-08-09 12:17:34 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,487,069 · 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x2bc437df…a6c7
0x34b655…2a6f
4 touches
1 conflict
0xd895ee0b…d301
0x34b655…2a6f
4 touches
1 conflict
0x0b05d77e…6f90
0x34b655…2a6f
2 touches
0 conflicts
0x1ffbed17…4f3c
0x34b655…2a6f
2 touches
0 conflicts
0x32b804b3…ce18
0x34b655…2a6f
2 touches
0 conflicts
0x4a9fb74d…af3b
0x34b655…2a6f
2 touches
0 conflicts
0x5c97b050…fed5
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity