← previous blocknext block →recent activity
Analyzing
Block #104,194,699
23 transactions · 23 stateful · 2026-09-12 13:44:30 UTC
Parallelism
52/100
Blocked
52%
Avg conflicts / tx
2.61
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #104,194,699 · 23 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w210w411w512w613w715w816w918w1019w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51a9c528…d9c3
0x34b655…2a6f
16 touches
28 conflicts
0x5d6da397…6c5c
0x34b655…2a6f
12 touches
15 conflicts
0xa33be62c…2c6a
0x34b655…2a6f
12 touches
15 conflicts
0xef048f92…572b
0x34b655…2a6f
8 touches
6 conflicts
0xa169711f…c7f3
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc2b37cdc…e470
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0x51a9c52857…bed9c3
Audit this contract →
← previous block·next block →recent activity