← previous blocknext block →recent activity
Analyzing
Block #102,414,086
12 transactions · 9 stateful · 2026-09-06 07:50:21 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,414,086 · 12 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
1w02w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd52cdd17…928b
0x99c7a7…8bf0
4 touches
1 conflict
0xdc7b9eda…e616
0x34b655…2a6f
4 touches
1 conflict
0xe32380a1…1db8
0x34b655…2a6f
4 touches
1 conflict
0xfaf89f45…ced6
0x34b655…2a6f
4 touches
1 conflict
0x5f0647bd…59b9
0x754704…b603
4 touches
1 conflict
0xa165a1e5…67be
0x754704…b603
4 touches
1 conflict
0xce62e150…1e09
0x754704…b603
4 touches
1 conflict
0xcf570cc1…b19c
0x99c7a7…8bf0
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: 0x99c7a72e…c78bf0
1 conflict on slot 0xd52cdd17f0…d5928b
Audit this contract →
← previous block·next block →recent activity