← previous blocknext block →recent activity
Analyzing
Block #100,432,850
20 transactions · 15 stateful · 2026-08-30 09:22:43 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,432,850 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
9w010w111w213w314w415w516w618w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcbe0757…afef
0x34b655…2a6f
10 touches
10 conflicts
0x97e4c862…4419
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xe569ddfe…86f9
0x34b655…2a6f
8 touches
6 conflicts
0xa9a9d0e0…4087
0x34b655…2a6f
6 touches
3 conflicts
0xb0e974c4…b84d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xfcbe075741…3aafef
Audit this contract →
← previous block·next block →recent activity