← previous blocknext block →recent activity
Analyzing
Block #101,800,058
17 transactions · 16 stateful · 2026-09-04 04:01:37 UTC
Parallelism
59/100
Blocked
44%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,800,058 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w39w012w114w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
12 touches
15 conflicts
0x0c60af1d…b1f9
0x34b655…2a6f
6 touches
3 conflicts
0x3027f5b0…7a3f
0x34b655…2a6f
6 touches
3 conflicts
0x3d13406e…eff1
0x34b655…2a6f
6 touches
3 conflicts
0x4dffc33e…068d
0x34b655…2a6f
6 touches
3 conflicts
0x4f3cc09a…2804
0x34b655…2a6f
6 touches
3 conflicts
0x53e08444…d671
0x34b655…2a6f
6 touches
3 conflicts
0x7dd96c96…7335
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity