← previous blocknext block →recent activity
Analyzing
Block #100,123,639
11 transactions · 11 stateful · 2026-08-29 07:22:50 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,123,639 · 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
2w08w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0x16d77246…bac5
0x34b655…2a6f
4 touches
1 conflict
0x6ef345ef…c927
0x34b655…2a6f
4 touches
1 conflict
0x7083c381…0ce7
0x34b655…2a6f
4 touches
1 conflict
0x77314e0b…77b5
0x34b655…2a6f
4 touches
1 conflict
0xada087b9…4aca
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
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
1 conflict on slot 0x261cbea79d…12e35e
Audit this contract →
← previous block·next block →recent activity