← previous blocknext block →recent activity
Analyzing
Block #110,329,233
36 transactions · 33 stateful · 2026-10-04 00:58:03 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
1.03
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #110,329,233 · 36 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w17w08w19w010w112w213w314w415w016w119w522w228w134w335w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x125f12…a50b
12 touches
15 conflicts
0x8240d70c…7c3b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x3643741b…109c
0x34b655…2a6f
4 touches
1 conflict
0x366a19b0…f065
0x34b655…2a6f
4 touches
1 conflict
0x4ae4b486…d0ec
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: 0x125f12a1…cda50b
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity