← previous blocknext block →recent activity
Analyzing
Block #99,116,739
15 transactions · 15 stateful · 2026-08-25 18:40:36 UTC
Parallelism
87/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,116,739 · 15 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
1w03w04w17w09w010w111w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x30c5329c…711c
0x34b655…2a6f
4 touches
1 conflict
0x36126dcb…ca1e
0x34b655…2a6f
4 touches
1 conflict
0x4c9e7249…1791
0x34b655…2a6f
4 touches
1 conflict
0x5f02b9d7…2a5f
0x34b655…2a6f
4 touches
1 conflict
0x6d15aba9…eb7b
0x34b655…2a6f
4 touches
1 conflict
0x76c75f52…0ad9
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
1 conflict on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity