← previous blocknext block →recent activity
Analyzing
Block #93,503,099
17 transactions · 17 stateful · 2026-08-06 01:33:10 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,503,099 · 17 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
1w02w14w05w17w08w29w312w214w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf18c12c4…3e7d
0x34b655…2a6f
4 touches
1 conflict
0xa1ff0729…0146
0xa6afd3…d132
4 touches
1 conflict
0x890a1db9…1712
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x1c014d01…fac5
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x342fc7e5…c7c7
0x34b655…2a6f
4 touches
1 conflict
0x53a7ea0d…090f
0x34b655…2a6f
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
1 conflict on slot 0xf18c12c49b…993e7d
Audit this contract →
← previous block·next block →recent activity