← previous blocknext block →recent activity
Analyzing
Block #102,817,221
31 transactions · 24 stateful · 2026-09-07 17:49:46 UTC
Parallelism
87/100
Blocked
46%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,817,221 · 31 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w16w27w08w014w015w119w120w222w323w225w026w127w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676f9f01…a8ac
0x34b655…2a6f
8 touches
6 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xc5aa10f4…c1a4
0x065c9d…c394
5 touches
3 conflicts
0x15698ac9…2a46
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x489646ad…1521
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
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 0x676f9f01ee…dea8ac
Audit this contract →
← previous block·next block →recent activity