← previous blocknext block →recent activity
Analyzing
Block #104,192,415
15 transactions · 15 stateful · 2026-09-12 13:32:50 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,192,415 · 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
2w03w14w25w09w110w211w212w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61040602…03b4
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x40970e69…da50
0x34ae4d…3fc5
6 touches
3 conflicts
0x55012d1a…3907
0x34ae4d…3fc5
6 touches
3 conflicts
0xb5c4826d…bdd6
0x34ae4d…3fc5
6 touches
3 conflicts
0x0b104f98…d9ee
0xc8689a…ee79
6 touches
3 conflicts
0xabde8104…c9a9
0x2a68ba…90c5
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
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 0x6104060294…7a03b4
Audit this contract →
← previous block·next block →recent activity