← previous blocknext block →recent activity
Analyzing
Block #104,870,160
24 transactions · 23 stateful · 2026-09-14 22:48:05 UTC
Parallelism
63/100
Blocked
61%
Avg conflicts / tx
1.29
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #104,870,160 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w07w18w29w310w411w113w514w615w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c68d10b…8386
0x34b655…2a6f
14 touches
21 conflicts
0x55f15e8f…f9a5
0x34b655…2a6f
10 touches
10 conflicts
0xcd93b2d2…30e6
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x0d5475fb…c455
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd7908b5f…56b9
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…8313
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
21 conflicts on slot 0x7c68d10b83…628386
Audit this contract →
← previous block·next block →recent activity