← previous blocknext block →recent activity
Analyzing
Block #106,377,684
24 transactions · 22 stateful · 2026-09-20 05:17:52 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,377,684 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w08w19w111w216w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x626418b6…20b6
0x3bd359…433a
4 touches
1 conflict
0xd737ce5d…5a95
0x3bd359…433a
4 touches
1 conflict
0x1c5c6a3b…5e1e
0x065c9d…c394
4 touches
1 conflict
0x6ee20f43…3b53
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x0a439a…0e3c
4 touches
1 conflict
0x00000000…0007
0x0a439a…0e3c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0x626418b61c…3020b6
Audit this contract →
← previous block·next block →recent activity