← previous blocknext block →recent activity
Analyzing
Block #100,586,408
17 transactions · 16 stateful · 2026-08-30 22:15:19 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.35
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,586,408 · 17 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
1w02w03w15w06w18w112w014w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1ac5a56…17d8
0x99c7a7…8bf0
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xe61a3df2…f763
0x34b655…2a6f
4 touches
1 conflict
0x49f39582…ccc7
0x754704…b603
4 touches
1 conflict
0xad47b33d…500b
0x754704…b603
4 touches
1 conflict
0xf00d2133…d68e
0x754704…b603
4 touches
1 conflict
0x48961b46…3dad
0x99c7a7…8bf0
4 touches
1 conflict
0x7e5ea60a…c4aa
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: 0x99c7a72e…c78bf0
1 conflict on slot 0xa1ac5a568a…af17d8
Audit this contract →
← previous block·next block →recent activity