← previous blocknext block →recent activity
Analyzing
Block #104,149,461
19 transactions · 18 stateful · 2026-09-12 09:54:54 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
1.79
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,149,461 · 19 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
1w02w13w24w311w412w513w615w416w517w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x705a9a1a…db08
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x64275949…d698
0x34b655…2a6f
6 touches
3 conflicts
0x41bfea99…ac66
0x34b655…2a6f
6 touches
3 conflicts
0x23f382f2…f742
0x34b655…2a6f
6 touches
3 conflicts
0xf39bd08b…d150
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
15 conflicts on slot 0x705a9a1af8…69db08
Audit this contract →
← previous block·next block →recent activity