← previous blocknext block →recent activity
Analyzing
Block #104,148,532
16 transactions · 16 stateful · 2026-09-12 09:50:11 UTC
Parallelism
50/100
Blocked
44%
Avg conflicts / tx
1.44
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,148,532 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w29w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1408e7c7…f324
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x6c0e32fc…a6ca
0x34b655…2a6f
6 touches
3 conflicts
0x8aeebcbe…1eb9
0x34b655…2a6f
6 touches
3 conflicts
0xa1f6215f…5d32
0x34b655…2a6f
6 touches
3 conflicts
0x69d5a4e5…350f
0x34b655…2a6f
4 touches
1 conflict
0x8f63f383…6eda
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
15 conflicts on slot 0x1408e7c773…87f324
Audit this contract →
← previous block·next block →recent activity