← previous blocknext block →recent activity
Analyzing
Block #100,811,462
19 transactions · 16 stateful · 2026-08-31 17:07:37 UTC
Parallelism
79/100
Blocked
25%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,811,462 · 19 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
2w03w05w19w110w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b0611f7…e63a
0x34b655…2a6f
6 touches
3 conflicts
0xd814f518…f5b4
0x34b655…2a6f
6 touches
3 conflicts
0xe9b595f2…ce42
0x34b655…2a6f
4 touches
1 conflict
0xec3a63b4…29ce
0x34b655…2a6f
4 touches
1 conflict
0x0168baa0…940f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0x0b0611f77e…54e63a
Audit this contract →
← previous block·next block →recent activity