← previous blocknext block →recent activity
Analyzing
Block #104,193,860
10 transactions · 10 stateful · 2026-09-12 13:40:09 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,193,860 · 10 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
4w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcea40325…6b39
0x34b655…2a6f
6 touches
3 conflicts
0x4ffb5637…e5c4
0x34b655…2a6f
6 touches
3 conflicts
0xf72228f6…970c
0x34b655…2a6f
4 touches
1 conflict
0x39126904…24d8
0x34b655…2a6f
4 touches
1 conflict
0xc4a231f6…4770
0x34b655…2a6f
4 touches
1 conflict
0x1507536e…933f
0x34b655…2a6f
2 touches
0 conflicts
0x1a2055c7…9054
0x34b655…2a6f
2 touches
0 conflicts
0x1a2055c7…9055
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
3 conflicts on slot 0xcea4032543…de6b39
Audit this contract →
← previous block·next block →recent activity