← previous blocknext block →recent activity
Analyzing
Block #100,031,197
12 transactions · 12 stateful · 2026-08-28 23:37:26 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,031,197 · 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
1w02w03w16w17w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcaaca573…465e
0x065c9d…c394
4 touches
1 conflict
0xff53b6b2…2f57
0x754704…b603
4 touches
1 conflict
0x0fb999ce…da22
0x754704…b603
4 touches
1 conflict
0x4e5afb3a…a338
0x3bd359…433a
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x7fc2b25e…26b9
0xd32edf…ff58
3 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
2 touches
0 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
2 touches
0 conflicts
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: Market-MON/USDC
1 conflict on slot 0xcaaca573bd…73465e
Audit this contract →
← previous block·next block →recent activity