← previous blocknext block →recent activity
Analyzing
Block #100,852,259
16 transactions · 14 stateful · 2026-08-31 20:33:03 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,852,259 · 16 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
1w02w03w04w15w26w39w010w113w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x5f77d607…2c84
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x06e40499…165e
0x34ae4d…3fc5
4 touches
1 conflict
0x10abefc9…c9bc
0x34ae4d…3fc5
4 touches
1 conflict
0x2a981bf0…9528
0x34ae4d…3fc5
4 touches
1 conflict
0x8cf3d245…1d0d
0x34ae4d…3fc5
4 touches
1 conflict
0xa605468c…1bfc
0x34ae4d…3fc5
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: Kuru Exchange: MarginAccount
6 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity