← previous blocknext block →recent activity
Analyzing
Block #104,876,645
17 transactions · 16 stateful · 2026-09-14 23:20:43 UTC
Parallelism
82/100
Blocked
31%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,876,645 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w08w09w110w113w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1ddcfe3f…9a06
0x754704…b603
4 touches
1 conflict
0x5943058d…92ee
0x754704…b603
4 touches
1 conflict
0xc39ff265…485e
0x34b655…2a6f
4 touches
1 conflict
0xe13ad55d…83b3
0x754704…b603
4 touches
1 conflict
0x2dc9d5d6…e671
0x99c7a7…8bf0
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
3 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity