← previous blocknext block →recent activity
Analyzing
Block #104,326,559
17 transactions · 16 stateful · 2026-09-13 00:53:31 UTC
Parallelism
59/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,326,559 · 17 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
4w05w08w19w210w311w413w514w416w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2531b293…51c6
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x1e737223…2278
0x34b655…2a6f
6 touches
3 conflicts
0xfb4f6c11…7103
0x34b655…2a6f
6 touches
3 conflicts
0x3f69a06e…566f
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x6719a767…9d62
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
10 conflicts on slot 0x2531b29338…f851c6
Audit this contract →
← previous block·next block →recent activity