← previous blocknext block →recent activity
Analyzing
Block #101,802,913
13 transactions · 11 stateful · 2026-09-04 04:15:59 UTC
Parallelism
85/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,802,913 · 13 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
1w02w13w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44696fac…44d6
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xcc9c918e…76f2
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xe61a3df2…f763
0x34b655…2a6f
4 touches
1 conflict
0x7f5b2c1d…0e7f
0x34b655…2a6f
2 touches
0 conflicts
0x80f20ca5…e72b
0x34b655…2a6f
2 touches
0 conflicts
0x82aab117…59f2
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 0x44696facb1…1e44d6
Audit this contract →
← previous block·next block →recent activity