← previous blocknext block →recent activity
Analyzing
Block #104,983,741
20 transactions · 20 stateful · 2026-09-15 08:19:37 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,983,741 · 20 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
1w02w13w14w05w16w07w18w29w310w414w015w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x3a68d7c1…372f
0x34b655…2a6f
10 touches
10 conflicts
0x706c758c…2fdb
0x34b655…2a6f
10 touches
10 conflicts
0x99e63c7a…26b8
0x34b655…2a6f
10 touches
10 conflicts
0xa7ecbbe7…f713
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xd5b10148…e637
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
10 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity