← previous blocknext block →recent activity
Analyzing
Block #100,812,365
28 transactions · 19 stateful · 2026-08-31 17:12:10 UTC
Parallelism
82/100
Blocked
37%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,812,365 · 28 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
1w02w17w08w111w012w114w215w216w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe95b60b…ef36
0x34b655…2a6f
8 touches
6 conflicts
0xb1856468…e84f
0x34b655…2a6f
6 touches
3 conflicts
0xba1edffb…323e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd18a8dca…452c
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 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: Perpl
6 conflicts on slot 0xfe95b60b07…fbef36
Audit this contract →
← previous block·next block →recent activity