← previous blocknext block →recent activity
Analyzing
Block #99,260,874
19 transactions · 19 stateful · 2026-08-26 06:45:55 UTC
Parallelism
89/100
Blocked
11%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,260,874 · 19 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
6w08w110w016w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0xb6fcbbb7…2b31
0x34b655…2a6f
4 touches
1 conflict
0xc6b65f73…ab6d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x46483cb1…e7ca
0x34b655…2a6f
4 touches
1 conflict
0xa0791758…d6a1
0x065c9d…c394
2 touches
0 conflicts
0xa63f8c9e…a1ea
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
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 0x85a88798de…47f85e
Audit this contract →
← previous block·next block →recent activity