← previous blocknext block →recent activity
Analyzing
Block #102,413,681
16 transactions · 16 stateful · 2026-09-06 07:48:19 UTC
Parallelism
81/100
Blocked
19%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,413,681 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w08w110w214w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdba64e01…a680
0x34b655…2a6f
6 touches
3 conflicts
0xd6113c0f…0a4b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x1a2055c7…9054
0x34b655…2a6f
4 touches
1 conflict
0x24b08f9c…e594
0x34b655…2a6f
4 touches
1 conflict
0x640c4fb2…044a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0xdba64e01ac…80a680
Audit this contract →
← previous block·next block →recent activity