← previous blocknext block →recent activity
Analyzing
Block #104,023,533
15 transactions · 15 stateful · 2026-09-11 23:14:09 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,023,533 · 15 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
2w03w04w18w29w311w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfa8d1a6…c43c
0x34b655…2a6f
8 touches
6 conflicts
0x30908823…a62d
0x34b655…2a6f
6 touches
3 conflicts
0xc38f85b7…ae91
0x34b655…2a6f
6 touches
3 conflicts
0x898d9b8a…d1ef
0x34b655…2a6f
6 touches
3 conflicts
0x7b42f6a7…f49c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1a3d2527…8ca0
0x34b655…2a6f
4 touches
1 conflict
0x3e3f27ce…580c
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 0xbfa8d1a6d4…52c43c
Audit this contract →
← previous block·next block →recent activity