← previous blocknext block →recent activity
Analyzing
Block #100,748,169
21 transactions · 20 stateful · 2026-08-31 11:49:01 UTC
Parallelism
76/100
Blocked
30%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,748,169 · 21 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
2w08w111w213w214w315w420w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e5ba496…66d5
0x34b655…2a6f
8 touches
6 conflicts
0x25180879…8191
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x038b9243…553d
0x34b655…2a6f
4 touches
1 conflict
0x2dd362aa…f84f
0x34b655…2a6f
4 touches
1 conflict
0x67a56c8b…f955
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 0x0e5ba496ad…a566d5
Audit this contract →
← previous block·next block →recent activity