← previous blocknext block →recent activity
Analyzing
Block #102,856,314
34 transactions · 30 stateful · 2026-09-07 21:06:30 UTC
Parallelism
59/100
Blocked
57%
Avg conflicts / tx
2.88
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #102,856,314 · 34 txs across 14 waves · depth 14
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
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w111w012w113w215w020w121w223w324w425w526w627w728w829w930w1031w1132w1233w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
28 touches
91 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
18 touches
36 conflicts
0x7dd96c96…7335
0x34b655…2a6f
18 touches
36 conflicts
0x51fc8795…126f
0x34b655…2a6f
18 touches
36 conflicts
0x045532dd…4b7d
0x34b655…2a6f
10 touches
10 conflicts
0xb069ae3b…f861
0x851145…3f07
6 touches
3 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
6 touches
3 conflicts
0x3b25d07f…1dee
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
91 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity