← previous blocknext block →recent activity
Analyzing
Block #104,977,350
22 transactions · 22 stateful · 2026-09-15 07:47:28 UTC
Parallelism
82/100
Blocked
36%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,977,350 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w08w110w011w112w213w014w117w018w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60d3cf20…db3f
0x34b655…2a6f
6 touches
3 conflicts
0x61ca6437…2142
0x34b655…2a6f
6 touches
3 conflicts
0xcd5c0ecb…4b5f
0x34b655…2a6f
6 touches
3 conflicts
0x0fd9f955…e86b
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
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 0x60d3cf2090…5cdb3f
Audit this contract →
← previous block·next block →recent activity