← previous blocknext block →recent activity
Analyzing
Block #101,973,817
31 transactions · 24 stateful · 2026-09-04 18:39:05 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.61
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,973,817 · 31 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
8w09w114w215w316w417w518w221w628w529w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x19c825c0…80f3
0x34b655…2a6f
8 touches
6 conflicts
0xcdbcbb1e…b5d2
0x34b655…2a6f
8 touches
6 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
6 touches
3 conflicts
0x155e52ca…fac7
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity