← previous blocknext block →recent activity
Analyzing
Block #100,561,284
22 transactions · 18 stateful · 2026-08-30 20:08:56 UTC
Parallelism
86/100
Blocked
28%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,561,284 · 22 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
5w07w113w014w116w117w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65732663…3bc3
0x8964d7…10f8
4 touches
1 conflict
0x65732663…3bc4
0x8964d7…10f8
4 touches
1 conflict
0x65732663…3bc6
0x8964d7…10f8
4 touches
1 conflict
0x6324ccc9…14fd
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xea57afd0…4232
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 0x6573266316…093bc3
Audit this contract →
← previous block·next block →recent activity