← previous blocknext block →recent activity
Analyzing
Block #104,200,968
15 transactions · 14 stateful · 2026-09-12 14:16:23 UTC
Parallelism
87/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #104,200,968 · 15 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
1w05w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4481c5db…6d99
0x34b655…2a6f
4 touches
1 conflict
0xb73bc4d0…c656
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1408e7c7…f324
0x34b655…2a6f
4 touches
1 conflict
0x4e135144…4167
0x34b655…2a6f
2 touches
0 conflicts
0x6f8644f7…10fa
0x34b655…2a6f
2 touches
0 conflicts
0x73e9d728…db58
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 0x4481c5dbdd…3f6d99
Audit this contract →
← previous block·next block →recent activity