← previous blocknext block →recent activity
Analyzing
Block #94,279,328
14 transactions · 11 stateful · 2026-08-08 18:43:13 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,279,328 · 14 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
3w04w15w06w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b30a6e6…b249
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0xd192f4ed…d7ec
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x3acc628e…e425
0x34b655…2a6f
2 touches
0 conflicts
0x5502e1cc…3910
0x34b655…2a6f
2 touches
0 conflicts
0x6283f415…d5c8
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 0x5b30a6e65f…9bb249
Audit this contract →
← previous block·next block →recent activity