← previous blocknext block →recent activity
Analyzing
Block #102,107,736
12 transactions · 10 stateful · 2026-09-05 05:58:05 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,107,736 · 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
6w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36836f22…9649
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x09d37b48…12a2
0x34b655…2a6f
3 touches
1 conflict
0xab2f6eed…254b
0x188d58…ea8e
2 touches
0 conflicts
0x31d88d27…7617
0x34b655…2a6f
2 touches
0 conflicts
0x3cd6dc90…823e
0x34b655…2a6f
2 touches
0 conflicts
0x46356904…5ead
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 0x36836f22bf…f19649
Audit this contract →
← previous block·next block →recent activity