← previous blocknext block →recent activity
Analyzing
Block #104,810,907
17 transactions · 17 stateful · 2026-09-14 17:48:57 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,810,907 · 17 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
1w02w13w06w17w08w211w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x2c204023…8806
0x754704…b603
4 touches
1 conflict
0x6726896b…7935
0x754704…b603
4 touches
1 conflict
0x6c54aa60…40ec
0x754704…b603
4 touches
1 conflict
0x4be64d14…06ba
0x99c7a7…8bf0
4 touches
1 conflict
0x5604386a…eec9
0x99c7a7…8bf0
4 touches
1 conflict
0x64d501ff…42cf
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity