← previous blocknext block →recent activity
Analyzing
Block #104,877,510
22 transactions · 20 stateful · 2026-09-14 23:25:05 UTC
Parallelism
77/100
Blocked
45%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,877,510 · 22 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
1w04w17w28w19w010w113w314w415w016w117w018w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81716ce9…095f
0x34b655…2a6f
10 touches
10 conflicts
0x7598abcc…868f
0x34b655…2a6f
8 touches
6 conflicts
0x1b6712ab…2da8
0x34b655…2a6f
6 touches
3 conflicts
0x42523a73…c021
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
0x34b655…2a6f
4 touches
1 conflict
0x9f9673a1…1f9b
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 0x81716ce924…61095f
Audit this contract →
← previous block·next block →recent activity