← previous blocknext block →recent activity
Analyzing
Block #100,699,636
18 transactions · 17 stateful · 2026-08-31 07:44:53 UTC
Parallelism
89/100
Blocked
29%
Avg conflicts / tx
0.28
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,699,636 · 18 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
1w03w16w09w011w112w113w014w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8c9e562…98c9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xa987699f…eabe
0x34ae4d…3fc5
2 touches
0 conflicts
0xe2263bea…6a9d
0x34ae4d…3fc5
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: Perpl
1 conflict on slot 0xa8c9e5620f…1498c9
Audit this contract →
← previous block·next block →recent activity