← previous blocknext block →recent activity
Analyzing
Block #104,024,344
16 transactions · 16 stateful · 2026-09-11 23:18:16 UTC
Parallelism
75/100
Blocked
19%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,024,344 · 16 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
1w04w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcea5e966…88fd
0x34b655…2a6f
8 touches
6 conflicts
0x30908823…a62d
0x34b655…2a6f
8 touches
6 conflicts
0xb46bb9bf…deb7
0x34b655…2a6f
4 touches
1 conflict
0x24b08f9c…e594
0x34b655…2a6f
4 touches
1 conflict
0x361f4a1b…1f14
0x34b655…2a6f
4 touches
1 conflict
0xcb45d9d6…cb83
0x1b6862…e19c
2 touches
0 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
6 conflicts on slot 0xcea5e9660d…8188fd
Audit this contract →
← previous block·next block →recent activity