← previous blocknext block →recent activity
Analyzing
Block #100,140,101
9 transactions · 7 stateful · 2026-08-29 08:45:50 UTC
Parallelism
56/100
Blocked
57%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,140,101 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w37w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a12c8b2…43e5
0x34b655…2a6f
6 touches
3 conflicts
0xdc8d7edd…8a03
0x34b655…2a6f
4 touches
1 conflict
0x50c61506…343f
0x34b655…2a6f
4 touches
1 conflict
0xf9874e36…beed
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe3078e0e…0496
0x34b655…2a6f
4 touches
1 conflict
0x6b267bdf…b173
0x34b655…2a6f
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
3 conflicts on slot 0x4a12c8b287…9b43e5
Audit this contract →
← previous block·next block →recent activity