← previous blocknext block →recent activity
Analyzing
Block #104,810,991
21 transactions · 18 stateful · 2026-09-14 17:49:22 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
0.43
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,810,991 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w06w18w29w312w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc33f505…fb22
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x059e0ac0…0267
0x34b655…2a6f
4 touches
1 conflict
0x1002d20f…b67a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x4118bd12…924a
0x34b655…2a6f
4 touches
1 conflict
0x941bd594…21fd
0x34b655…2a6f
4 touches
1 conflict
0x6cd6078c…7e9b
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
3 conflicts on slot 0xbc33f505c6…d2fb22
Audit this contract →
← previous block·next block →recent activity