← previous blocknext block →recent activity
Analyzing
Block #104,803,954
22 transactions · 20 stateful · 2026-09-14 17:13:56 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,803,954 · 22 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
1w02w14w05w16w28w313w314w415w317w521w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2202504e…fad0
0x34b655…2a6f
8 touches
6 conflicts
0x55010ec8…ea31
0x34b655…2a6f
8 touches
6 conflicts
0x5fad6fee…7714
0x34b655…2a6f
6 touches
3 conflicts
0xba9f9225…2ead
0x34b655…2a6f
6 touches
3 conflicts
0xf081c170…f590
0x34b655…2a6f
6 touches
3 conflicts
0x7b74ef7e…66b7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa69e7850…4482
0x34b655…2a6f
6 touches
3 conflicts
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 0x2202504ef1…9ffad0
Audit this contract →
← previous block·next block →recent activity