← previous blocknext block →recent activity
Analyzing
Block #104,704,637
8 transactions · 7 stateful · 2026-09-14 08:52:40 UTC
Parallelism
50/100
Blocked
57%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,704,637 · 8 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w37w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x082a85db…aade
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xe92f93fd…4515
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x46a49ab4…d527
0x34b655…2a6f
4 touches
1 conflict
0x56a7b140…4718
0x34b655…2a6f
4 touches
1 conflict
0x91329f32…997e
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
1 conflict on slot 0x082a85dbf5…c7aade
Audit this contract →
← previous block·next block →recent activity