← previous blocknext block →recent activity
Analyzing
Block #100,982,351
24 transactions · 22 stateful · 2026-09-01 07:27:25 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,982,351 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
9w010w111w215w016w317w018w119w221w022w123w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd814f518…f5b4
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x5d8975d1…341a
0x34b655…2a6f
6 touches
3 conflicts
0x641aed07…bcb9
0x34b655…2a6f
4 touches
1 conflict
0x14fb4c2a…2d8d
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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
6 conflicts on slot 0xd814f51828…c6f5b4
Audit this contract →
← previous block·next block →recent activity