← previous blocknext block →recent activity
Analyzing
Block #101,300,613
23 transactions · 19 stateful · 2026-09-02 10:08:57 UTC
Parallelism
87/100
Blocked
32%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,300,613 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w114w015w116w118w221w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x502b3ee1…7f7c
0x34b655…2a6f
6 touches
3 conflicts
0x86bd79a5…1f48
0x34b655…2a6f
6 touches
3 conflicts
0xef4aebaf…94cd
0x34b655…2a6f
4 touches
1 conflict
0x6b267bdf…b173
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xecd87a39…d9c5
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
3 conflicts on slot 0x502b3ee1e6…227f7c
Audit this contract →
← previous block·next block →recent activity