← previous blocknext block →recent activity
Analyzing
Block #102,640,951
37 transactions · 35 stateful · 2026-09-07 02:59:44 UTC
Parallelism
68/100
Blocked
74%
Avg conflicts / tx
1.7
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #102,640,951 · 37 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w16w27w08w19w211w212w314w115w319w121w422w223w424w325w526w527w128w129w231w632w735w1036w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x0d2d23d3…8a3a
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x736b9166…5ea5
0x34b655…2a6f
8 touches
6 conflicts
0xa1bfcd69…07cf
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xe937b6bc…8a5b
0x1b6862…e19c
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity