← previous blocknext block →recent activity
Analyzing
Block #102,156,509
16 transactions · 16 stateful · 2026-09-05 10:05:17 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
1.94
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,156,509 · 16 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
1w02w04w06w09w110w211w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff324fdb…4bc0
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x939cdd56…00c8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xa4e9800f…4ab0
0x34b655…2a6f
6 touches
3 conflicts
0x1db5837f…1264
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x18e86f02…fa98
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
15 conflicts on slot 0xff324fdb5e…bf4bc0
Audit this contract →
← previous block·next block →recent activity