← previous blocknext block →recent activity
Analyzing
Block #94,809,937
16 transactions · 16 stateful · 2026-08-10 15:22:59 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,809,937 · 16 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
4w05w06w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xa3a621f8…75a2
0x34b655…2a6f
4 touches
1 conflict
0x3944526b…c457
0x34b655…2a6f
2 touches
0 conflicts
0x54998534…d4dd
0x34b655…2a6f
2 touches
0 conflicts
0x5da1bb4d…628d
0x34b655…2a6f
2 touches
0 conflicts
0x6d9d9ff1…c03f
0x34b655…2a6f
2 touches
0 conflicts
0x98285344…4662
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 0x4acbdbcf7f…d0a8c6
Audit this contract →
← previous block·next block →recent activity