← previous blocknext block →recent activity
Analyzing
Block #100,160,465
12 transactions · 12 stateful · 2026-08-29 10:28:22 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,160,465 · 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
1w03w04w16w07w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa02175ba…c0f2
0x8964d7…10f8
4 touches
1 conflict
0xa02175ba…c0ef
0x8964d7…10f8
4 touches
1 conflict
0xa02175ba…c0f0
0x8964d7…10f8
4 touches
1 conflict
0x191e0467…70e5
0x34b655…2a6f
4 touches
1 conflict
0x33649c4f…b327
0x34b655…2a6f
4 touches
1 conflict
0x52e0faa1…d718
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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: 0x8964d7c9…5b10f8
1 conflict on slot 0xa02175ba3b…7bc0f2
Audit this contract →
← previous block·next block →recent activity