← previous blocknext block →recent activity
Analyzing
Block #99,184,683
18 transactions · 14 stateful · 2026-08-26 00:22:30 UTC
Parallelism
89/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,184,683 · 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
5w013w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8311570f…5321
0x34b655…2a6f
4 touches
1 conflict
0xd957b700…32be
0x34b655…2a6f
4 touches
1 conflict
0x4b54bf38…d5b6
0x34b655…2a6f
2 touches
0 conflicts
0x52595aab…b5f6
0x34b655…2a6f
2 touches
0 conflicts
0x5326f4c5…d9fd
0x34b655…2a6f
2 touches
0 conflicts
0x62bce8b9…c530
0x34b655…2a6f
2 touches
0 conflicts
0x706c758c…2fdb
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity