← previous blocknext block →recent activity
Analyzing
Block #93,074,536
33 transactions · 26 stateful · 2026-08-04 13:37:34 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,074,536 · 33 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w27w08w112w013w119w120w222w023w125w131w332w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb39cb1d8…effa
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x91855e…ac7e
6 touches
3 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x94de4d05…ad01
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x9375a764…dca1
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
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
6 conflicts on slot 0xb39cb1d8c6…28effa
Audit this contract →
← previous block·next block →recent activity