← previous blocknext block →recent activity
Analyzing
Block #101,988,089
21 transactions · 18 stateful · 2026-09-04 19:51:31 UTC
Parallelism
90/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,988,089 · 21 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w114w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6d0e119…6a6a
0x99c7a7…8bf0
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x25c0f8b5…4246
0x754704…b603
4 touches
1 conflict
0x8226c92c…ece7
0x754704…b603
4 touches
1 conflict
0xe4940a46…26a0
0x754704…b603
4 touches
1 conflict
0x3b9910a2…6177
0x99c7a7…8bf0
4 touches
1 conflict
0x0e236478…da55
0x34b655…2a6f
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: 0x99c7a72e…c78bf0
1 conflict on slot 0xd6d0e119a5…be6a6a
Audit this contract →
← previous block·next block →recent activity