← previous blocknext block →recent activity
Analyzing
Block #101,990,803
17 transactions · 16 stateful · 2026-09-04 20:05:20 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,990,803 · 17 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
1w02w14w15w26w07w112w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6be05f69…33d9
0x34b655…2a6f
6 touches
3 conflicts
0x8849e72f…b522
0x34b655…2a6f
6 touches
3 conflicts
0x6e7eb884…4fab
0x34b655…2a6f
6 touches
3 conflicts
0x8fd9063d…2f57
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x10c19272…7441
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x04d4f30d…4dfb
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 0x6be05f6972…0a33d9
Audit this contract →
← previous block·next block →recent activity