← previous blocknext block →recent activity
Analyzing
Block #100,096,051
29 transactions · 17 stateful · 2026-08-29 05:03:54 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,096,051 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w38w09w117w427w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06e40499…165e
0x2b46c0…1669
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xbb97db90…4c93
0xc8689a…ee79
8 touches
6 conflicts
0xa605468c…1bfc
0x2b46c0…1669
8 touches
6 conflicts
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
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: 0x2b46c08c…ec1669
6 conflicts on slot 0x06e40499d4…18165e
Audit this contract →
← previous block·next block →recent activity