← previous blocknext block →recent activity
Analyzing
Block #104,203,124
20 transactions · 20 stateful · 2026-09-12 14:27:20 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
1.55
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,203,124 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w36w08w09w110w411w512w613w715w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd1306ad…f1b8
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x7065ef11…461a
0x34b655…2a6f
8 touches
6 conflicts
0x0b6ad60b…a09d
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x6e6a8155…9636
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x06386625…6129
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
28 conflicts on slot 0xcd1306adf3…44f1b8
Audit this contract →
← previous block·next block →recent activity