← previous blocknext block →recent activity
Analyzing
Block #100,135,685
17 transactions · 15 stateful · 2026-08-29 08:23:32 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,135,685 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w111w013w214w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa605468c…1bfc
0x2b46c0…1669
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x5164ab0e…01e1
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb9868b52…c77f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x06e40499…165e
0x2b46c0…1669
4 touches
1 conflict
0x8bf9ff29…37a0
0xd32edf…ff58
3 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: 0x2b46c08c…ec1669
1 conflict on slot 0xa605468c6d…6d1bfc
Audit this contract →
← previous block·next block →recent activity