← previous blocknext block →recent activity
Analyzing
Block #100,790,857
25 transactions · 18 stateful · 2026-08-31 15:23:56 UTC
Parallelism
84/100
Blocked
22%
Avg conflicts / tx
0.24
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,790,857 · 25 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
1w07w110w012w117w218w019w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc9915b5…542c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0050
0x80c745…7210
4 touches
1 conflict
0xa03dbd5a…0c79
0x34b655…2a6f
4 touches
1 conflict
0xb2ae55b2…8912
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xecd87a39…d9c5
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…004f
0x80c745…7210
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: Perpl
3 conflicts on slot 0xdc9915b513…2b542c
Audit this contract →
← previous block·next block →recent activity