← previous blocknext block →recent activity
Analyzing
Block #104,847,309
19 transactions · 18 stateful · 2026-09-14 20:53:02 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,847,309 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w38w09w110w213w415w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c168b41…7486
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xa9bb6fd8…2877
0x34b655…2a6f
6 touches
3 conflicts
0xf05cf40a…dcc8
0x34b655…2a6f
6 touches
3 conflicts
0x5900e8aa…2391
0x34b655…2a6f
6 touches
3 conflicts
0x0799a0c6…0f72
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
6 conflicts on slot 0x9c168b41b3…567486
Audit this contract →
← previous block·next block →recent activity