← previous blocknext block →recent activity
Analyzing
Block #104,878,081
15 transactions · 15 stateful · 2026-09-14 23:27:57 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,878,081 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w09w110w211w312w013w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39f96589…5188
0x34b655…2a6f
8 touches
6 conflicts
0x8f63f383…6eda
0x34b655…2a6f
8 touches
6 conflicts
0x81716ce9…095f
0x34b655…2a6f
8 touches
6 conflicts
0xeb3b7095…3b55
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xc7799dc2…820b
0x34b655…2a6f
4 touches
1 conflict
0x07405812…0d81
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 0x39f965890f…985188
Audit this contract →
← previous block·next block →recent activity