← previous blocknext block →recent activity
Analyzing
Block #101,315,316
14 transactions · 13 stateful · 2026-09-02 11:22:56 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,315,316 · 14 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
12w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x886db264…846e
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x636b8021…5bef
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7e59f6d5…68f0
0x34b655…2a6f
3 touches
1 conflict
0x05732507…d5bf
0x34b655…2a6f
2 touches
0 conflicts
0x10f097a3…df27
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 0x886db2649c…07846e
Audit this contract →
← previous block·next block →recent activity