← previous blocknext block →recent activity
Analyzing
Block #99,496,427
18 transactions · 15 stateful · 2026-08-27 02:31:45 UTC
Parallelism
89/100
Blocked
27%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,496,427 · 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
1w02w13w05w18w010w011w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5982776…4846
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x5b09bf44…5907
0xa6afd3…d132
4 touches
1 conflict
0x4602f03a…2dae
0x34b655…2a6f
2 touches
0 conflicts
0x587c3223…8560
0x34b655…2a6f
2 touches
0 conflicts
0x5e2fca4c…cf4d
0x34b655…2a6f
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 0xd5982776a0…554846
Audit this contract →
← previous block·next block →recent activity