← previous blocknext block →recent activity
Analyzing
Block #101,672,413
19 transactions · 19 stateful · 2026-09-03 17:19:36 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
1.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,672,413 · 19 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
1w02w03w14w25w36w47w08w19w010w012w113w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67c1f465…38b3
0x34b655…2a6f
10 touches
10 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
10 touches
10 conflicts
0x4dffc33e…068d
0x34b655…2a6f
10 touches
10 conflicts
0xf36124ad…c08f
0x34b655…2a6f
10 touches
10 conflicts
0x1513b999…b52e
0x34b655…2a6f
10 touches
10 conflicts
0x3d13406e…eff1
0x34b655…2a6f
10 touches
10 conflicts
0x7fd951f1…fe49
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 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 0x67c1f46537…4d38b3
Audit this contract →
← previous block·next block →recent activity