← previous blocknext block →recent activity
Analyzing
Block #104,983,739
20 transactions · 19 stateful · 2026-09-15 08:19:37 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,983,739 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w29w310w411w514w015w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a68d7c1…372f
0x34b655…2a6f
12 touches
15 conflicts
0xa7ecbbe7…f713
0x34b655…2a6f
12 touches
15 conflicts
0x706c758c…2fdb
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x99e63c7a…26b8
0x34b655…2a6f
8 touches
6 conflicts
0x4f2983f2…5c28
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
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
15 conflicts on slot 0x3a68d7c1ee…ea372f
Audit this contract →
← previous block·next block →recent activity