← previous blocknext block →recent activity
Analyzing
Block #93,452,113
10 transactions · 9 stateful · 2026-08-05 21:16:51 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,452,113 · 10 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
1w04w15w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8743e1ba…8331
0x34b655…2a6f
4 touches
1 conflict
0x310afe2c…83e1
0x34b655…2a6f
4 touches
1 conflict
0xf0bd9219…d498
0x34b655…2a6f
4 touches
1 conflict
0x6507044e…bcd6
0x34b655…2a6f
4 touches
1 conflict
0x29a2aad6…286b
0x34b655…2a6f
2 touches
0 conflicts
0x34cdb3c2…96d2
0x34b655…2a6f
2 touches
0 conflicts
0x815f0791…b4d4
0x34b655…2a6f
2 touches
0 conflicts
0x820d9f0d…af3d
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 0x8743e1bab8…0a8331
Audit this contract →
← previous block·next block →recent activity