← previous blocknext block →recent activity
Analyzing
Block #99,199,613
19 transactions · 17 stateful · 2026-08-26 01:37:38 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,199,613 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w39w010w111w013w115w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2f74f175…9287
0x2b46c0…1669
4 touches
1 conflict
0x2f74f175…9288
0x2b46c0…1669
4 touches
1 conflict
0x2f74f175…9289
0x2b46c0…1669
4 touches
1 conflict
0x3ba7edbb…80e6
0x2b46c0…1669
4 touches
1 conflict
0x46279ae7…20dd
0x2b46c0…1669
4 touches
1 conflict
0x7f4a8466…f2cc
0x2b46c0…1669
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: 0xf5b5f7f8…a36d70
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity