← previous blocknext block →recent activity
Analyzing
Block #101,969,490
14 transactions · 14 stateful · 2026-09-04 18:17:12 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,969,490 · 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
1w02w13w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x5cb99fee…00cf
0x754704…b603
4 touches
1 conflict
0x9ae4aa46…597f
0x754704…b603
4 touches
1 conflict
0xde93ff88…37ec
0x754704…b603
4 touches
1 conflict
0x3dbaed38…1c8a
0x99c7a7…8bf0
4 touches
1 conflict
0x8881a9a9…b1ac
0x99c7a7…8bf0
4 touches
1 conflict
0x474b9623…8272
0x34b655…2a6f
2 touches
0 conflicts
0x4ab70ccd…2683
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 0x045532dd4b…244b7d
Audit this contract →
← previous block·next block →recent activity