← previous blocknext block →recent activity
Analyzing
Block #102,863,427
24 transactions · 19 stateful · 2026-09-07 21:42:17 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,863,427 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w011w212w113w217w321w422w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11b69a7e…334e
0x01bff4…1071
6 touches
3 conflicts
0x452fc62a…8841
0x34b655…2a6f
6 touches
3 conflicts
0xbad4e90b…33a5
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xd64f4b47…0c52
0x851145…3f07
5 touches
3 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
5 touches
3 conflicts
0xa87df366…0821
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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: 0x01bff417…bc1071
3 conflicts on slot 0x11b69a7ea1…83334e
Audit this contract →
← previous block·next block →recent activity