← previous blocknext block →recent activity
Analyzing
Block #100,144,325
24 transactions · 16 stateful · 2026-08-29 09:07:06 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,144,325 · 24 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
1w03w17w28w19w210w320w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50951f37…219c
0x3bd359…433a
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0003
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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: Wrapped MON (WMON)
1 conflict on slot 0x50951f3768…63219c
Audit this contract →
← previous block·next block →recent activity