← previous blocknext block →recent activity
Analyzing
Block #99,447,458
18 transactions · 16 stateful · 2026-08-26 22:25:10 UTC
Parallelism
89/100
Blocked
6%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,447,458 · 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x517a6935…e298
0x34b655…2a6f
3 touches
1 conflict
0x5492de24…e2e8
0x34b655…2a6f
3 touches
1 conflict
0x331ddc8d…a15c
0x065c9d…c394
2 touches
0 conflicts
0x343e4e81…c162
0x065c9d…c394
2 touches
0 conflicts
0x70935e43…c2a7
0x065c9d…c394
2 touches
0 conflicts
0xd2c437bf…f250
0x065c9d…c394
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 0x261cbea79d…12e35d
Audit this contract →
← previous block·next block →recent activity