← previous blocknext block →recent activity
Analyzing
Block #102,014,886
12 transactions · 11 stateful · 2026-09-04 22:07:25 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,014,886 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w16w07w110w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa90eb29b…2cec
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x0bb33e3f…7072
0x34b655…2a6f
2 touches
0 conflicts
0x10803fd3…2fd0
0x34b655…2a6f
2 touches
0 conflicts
0x2f17174f…68b4
0x34b655…2a6f
2 touches
0 conflicts
0x3027f5b0…7a3f
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xa90eb29b22…002cec
Audit this contract →
← previous block·next block →recent activity