← previous blocknext block →recent activity
Analyzing
Block #99,624,156
16 transactions · 16 stateful · 2026-08-27 13:21:33 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,624,156 · 16 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
1w03w05w06w17w111w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0x883b1ea6…2acf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x14def591…385e
0x851145…3f07
4 touches
1 conflict
0x9fe22cda…2c3a
0x851145…3f07
4 touches
1 conflict
0xd2b36119…e4e1
0x851145…3f07
4 touches
1 conflict
0xe957c63b…e347
0x851145…3f07
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 0x6ca15e14f4…917be8
Audit this contract →
← previous block·next block →recent activity