← previous blocknext block →recent activity
Analyzing
Block #104,149,758
13 transactions · 12 stateful · 2026-09-12 09:56:25 UTC
Parallelism
46/100
Blocked
50%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,149,758 · 13 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w39w410w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7844ba0b…0823
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x705a9a1a…db08
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7cf5c54d…589f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0x7844ba0b56…a40823
Audit this contract →
← previous block·next block →recent activity