← previous blocknext block →recent activity
Analyzing
Block #101,993,499
23 transactions · 23 stateful · 2026-09-04 20:18:59 UTC
Parallelism
74/100
Blocked
26%
Avg conflicts / tx
0.48
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,993,499 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w15w26w37w415w020w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe53bd661…5352
0x34b655…2a6f
8 touches
6 conflicts
0x5c7b5ec0…0764
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xb73a5ffd…ddee
0x34b655…2a6f
6 touches
3 conflicts
0xc0f6895c…e428
0x34b655…2a6f
6 touches
3 conflicts
0x2891f7b7…bc9c
0x34b655…2a6f
6 touches
3 conflicts
0xd98afa6e…3364
0x34b655…2a6f
6 touches
3 conflicts
0xda09bbc9…b41b
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xe53bd661fb…e85352
Audit this contract →
← previous block·next block →recent activity