← previous blocknext block →recent activity
Analyzing
Block #104,195,791
25 transactions · 23 stateful · 2026-09-12 13:50:02 UTC
Parallelism
76/100
Blocked
43%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,195,791 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w17w111w212w216w317w418w520w223w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc2493d3…6898
0x34b655…2a6f
8 touches
6 conflicts
0x45de70d9…e1dc
0x34b655…2a6f
8 touches
6 conflicts
0x14084a98…58b3
0x34b655…2a6f
6 touches
3 conflicts
0x67c69db9…7906
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x5d6da397…6c5c
0x34b655…2a6f
4 touches
1 conflict
0x7ac265cd…0253
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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
6 conflicts on slot 0xfc2493d371…f36898
Audit this contract →
← previous block·next block →recent activity