← previous blocknext block →recent activity
Analyzing
Block #104,867,714
15 transactions · 15 stateful · 2026-09-14 22:35:47 UTC
Parallelism
73/100
Blocked
53%
Avg conflicts / tx
0.87
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,867,714 · 15 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
1w02w13w14w05w16w210w211w212w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce74d807…8716
0x34b655…2a6f
8 touches
6 conflicts
0xa93fb268…e452
0x34b655…2a6f
6 touches
3 conflicts
0x3ee8b564…4c49
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4e5515f1…faec
0x34b655…2a6f
6 touches
3 conflicts
0x4d42f16e…a6ca
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
6 conflicts on slot 0xce74d80713…ab8716
Audit this contract →
← previous block·next block →recent activity