← previous blocknext block →recent activity
Analyzing
Block #104,024,602
18 transactions · 17 stateful · 2026-09-11 23:19:35 UTC
Parallelism
78/100
Blocked
24%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,024,602 · 18 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
2w013w114w216w317w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1321758b…6798
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x30908823…a62d
0x34b655…2a6f
6 touches
3 conflicts
0x361f4a1b…1f14
0x34b655…2a6f
6 touches
3 conflicts
0x7c354d5f…8911
0x34b655…2a6f
6 touches
3 conflicts
0xd1448207…452d
0x34b655…2a6f
4 touches
1 conflict
0xfc8cd993…5c11
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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
3 conflicts on slot 0x1321758ba2…df6798
Audit this contract →
← previous block·next block →recent activity