← previous blocknext block →recent activity
Analyzing
Block #102,016,116
12 transactions · 12 stateful · 2026-09-04 22:13:39 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,016,116 · 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
1w03w04w15w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x113a6203…5dd8
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0cc4c914…333b
0x34b655…2a6f
2 touches
0 conflicts
0x126036d8…3b50
0x34b655…2a6f
2 touches
0 conflicts
0x29a58269…011a
0x34b655…2a6f
2 touches
0 conflicts
0x2c062142…d50c
0x34b655…2a6f
2 touches
0 conflicts
0x3180d46a…db4e
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 0x113a62038a…805dd8
Audit this contract →
← previous block·next block →recent activity