← previous blocknext block →recent activity
Analyzing
Block #100,080,696
22 transactions · 22 stateful · 2026-08-29 03:46:36 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,080,696 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w09w112w113w216w317w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd895ee0b…d301
0x34b655…2a6f
6 touches
3 conflicts
0xa11b60f7…8e8b
0x34b655…2a6f
6 touches
3 conflicts
0xfbd3c598…8a21
0x34b655…2a6f
6 touches
3 conflicts
0xfc67c406…e655
0x34b655…2a6f
6 touches
3 conflicts
0x50c61506…343f
0x34b655…2a6f
4 touches
1 conflict
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
0x29354600…7b17
0x34b655…2a6f
4 touches
1 conflict
0x85bfd0af…ce96
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 0xd895ee0be4…14d301
Audit this contract →
← previous block·next block →recent activity