← previous blocknext block →recent activity
Analyzing
Block #101,502,703
11 transactions · 11 stateful · 2026-09-03 03:05:51 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,502,703 · 11 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
1w03w04w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0f6f4f2…dffa
0x34b655…2a6f
4 touches
1 conflict
0x62030a81…91be
0x34b655…2a6f
4 touches
1 conflict
0xfcc05e4b…f322
0x34b655…2a6f
4 touches
1 conflict
0x9b4280b3…1170
0x34b655…2a6f
4 touches
1 conflict
0x3dc5798b…5c87
0x34b655…2a6f
4 touches
1 conflict
0xce54f011…003c
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0028
0x1b6862…e19c
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 0xd0f6f4f225…4cdffa
Audit this contract →
← previous block·next block →recent activity