← previous blocknext block →recent activity
Analyzing
Block #101,314,601
18 transactions · 17 stateful · 2026-09-02 11:19:20 UTC
Parallelism
89/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,314,601 · 18 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
4w08w09w111w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97e86e6f…a5cc
0x34b655…2a6f
4 touches
1 conflict
0xec48840b…9ddc
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2f743f76…b35d
0x34b655…2a6f
2 touches
0 conflicts
0x52404f3d…4c2e
0x34b655…2a6f
2 touches
0 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
2 touches
0 conflicts
0x8fe09636…ac5a
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 0x97e86e6f22…31a5cc
Audit this contract →
← previous block·next block →recent activity