← previous blocknext block →recent activity
Analyzing
Block #101,985,063
10 transactions · 9 stateful · 2026-09-04 19:36:07 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,985,063 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9fe324c…70c7
0x34b655…2a6f
4 touches
1 conflict
0x2e957c13…4777
0x34b655…2a6f
4 touches
1 conflict
0x4113c42b…5765
0x34b655…2a6f
4 touches
1 conflict
0xf0e7ad63…ef51
0x34b655…2a6f
4 touches
1 conflict
0x1a22c3cc…bf90
0x34b655…2a6f
2 touches
0 conflicts
0x237bb249…b0a0
0x34b655…2a6f
2 touches
0 conflicts
0x2d02f869…1f83
0x34b655…2a6f
2 touches
0 conflicts
0x3380b0e7…3825
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 0xb9fe324c2b…7070c7
Audit this contract →
← previous block·next block →recent activity