← previous blocknext block →recent activity
Analyzing
Block #100,267,189
14 transactions · 14 stateful · 2026-08-29 19:26:57 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,267,189 · 14 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
3w06w07w08w110w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bb0d58d…9dcf
0x34b655…2a6f
4 touches
1 conflict
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0x43f6a6bc…9dd2
0x928dc8…8207
4 touches
1 conflict
0x43f6a6bc…9dd5
0x928dc8…8207
4 touches
1 conflict
0x43f6a6bc…9dd7
0x928dc8…8207
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4e0a9e70…bdb7
0x34b655…2a6f
4 touches
1 conflict
0x53ca1284…cb2c
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 0x2bb0d58d61…679dcf
Audit this contract →
← previous block·next block →recent activity