← previous blocknext block →recent activity
Analyzing
Block #100,613,387
22 transactions · 20 stateful · 2026-08-31 00:31:02 UTC
Parallelism
77/100
Blocked
50%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,613,387 · 22 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
2w03w17w09w110w211w312w114w116w217w318w421w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69ee875e…ea1e
0x34b655…2a6f
8 touches
6 conflicts
0xa6d40b7f…2969
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5581d709…ab77
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0xaf1337eb…92c3
0x34b655…2a6f
4 touches
1 conflict
0xb7ce83b1…2c96
0x34b655…2a6f
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
6 conflicts on slot 0x69ee875ef1…21ea1e
Audit this contract →
← previous block·next block →recent activity