← previous blocknext block →recent activity
Analyzing
Block #100,978,063
23 transactions · 18 stateful · 2026-09-01 07:05:51 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,978,063 · 23 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
2w03w14w26w014w015w116w218w019w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x315e07b8…9823
0x34b655…2a6f
8 touches
6 conflicts
0x0cf7f3e4…b4f4
0x34b655…2a6f
6 touches
3 conflicts
0x9d1f0c80…b5b4
0x34b655…2a6f
6 touches
3 conflicts
0x1a2e73cf…5ff5
0x34b655…2a6f
6 touches
3 conflicts
0xb5924647…4cf1
0x34b655…2a6f
6 touches
3 conflicts
0x024b482b…16b0
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
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 0x315e07b806…529823
Audit this contract →
← previous block·next block →recent activity