← previous blocknext block →recent activity
Analyzing
Block #100,589,071
20 transactions · 17 stateful · 2026-08-30 22:28:42 UTC
Parallelism
90/100
Blocked
12%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,589,071 · 20 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
1w07w09w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08e8f2c9…a11a
0x34b655…2a6f
4 touches
1 conflict
0x34aea08d…5127
0x34b655…2a6f
4 touches
1 conflict
0xc3172c3f…289f
0x34b655…2a6f
4 touches
1 conflict
0x5f0a01c3…8269
0x851145…3f07
4 touches
1 conflict
0x90b1f042…5833
0x851145…3f07
4 touches
1 conflict
0x08d53462…97ef
0x2b46c0…1669
2 touches
0 conflicts
0x39977254…07b1
0x2b46c0…1669
2 touches
0 conflicts
0x3a3e7727…36c5
0x2b46c0…1669
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 0x08e8f2c94d…1ca11a
Audit this contract →
← previous block·next block →recent activity