← previous blocknext block →recent activity
Analyzing
Block #99,446,263
19 transactions · 17 stateful · 2026-08-26 22:19:09 UTC
Parallelism
63/100
Blocked
59%
Avg conflicts / tx
0.68
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,446,263 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w15w26w27w39w410w011w113w217w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e8a6177…499b
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xb575cf74…fbd5
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfe6ff5a4…c639
0x34b655…2a6f
4 touches
1 conflict
0x07bb3f5a…617e
0x34b655…2a6f
4 touches
1 conflict
0x26ee1da7…3c2a
0x34b655…2a6f
4 touches
1 conflict
0x32530ce0…0a5f
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
3 conflicts on slot 0x8e8a617749…fc499b
Audit this contract →
← previous block·next block →recent activity