← previous blocknext block →recent activity
Analyzing
Block #104,326,569
15 transactions · 14 stateful · 2026-09-13 00:53:34 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,326,569 · 15 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
1w02w13w24w38w110w211w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x759871b5…8eaa
0x34b655…2a6f
8 touches
6 conflicts
0xaf30c163…0fb6
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa016f004…df70
0x34b655…2a6f
6 touches
3 conflicts
0xf788c790…e66f
0x34b655…2a6f
4 touches
1 conflict
0x4147b177…c9ba
0x34b655…2a6f
4 touches
1 conflict
0x705049f0…5022
0x34b655…2a6f
4 touches
1 conflict
0x7ef4ba09…2a25
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
6 conflicts on slot 0x759871b59a…7a8eaa
Audit this contract →
← previous block·next block →recent activity