← previous blocknext block →recent activity
Analyzing
Block #104,195,444
7 transactions · 7 stateful · 2026-09-12 13:48:17 UTC
Parallelism
57/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,195,444 · 7 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf394e6ad…f568
0x34b655…2a6f
4 touches
1 conflict
0xc4a231f6…4770
0x34b655…2a6f
4 touches
1 conflict
0x6e6a8155…9636
0x34b655…2a6f
4 touches
1 conflict
0xd3d41c87…c724
0x34b655…2a6f
4 touches
1 conflict
0x07d94be1…7fa8
0x34b655…2a6f
2 touches
0 conflicts
0x1565183a…e0a0
0x34b655…2a6f
2 touches
0 conflicts
0x201d7cf1…f7f2
0x34b655…2a6f
2 touches
0 conflicts
0x34cdb3c2…96d2
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xf394e6ad8c…57f568
Audit this contract →
← previous block·next block →recent activity