← previous blocknext block →recent activity
Analyzing
Block #96,544,558
17 transactions · 14 stateful · 2026-08-16 17:04:00 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,544,558 · 17 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
1w02w13w04w05w18w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xf0d45ffd…89cf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0xeaced15b…2221
0x754704…b603
4 touches
1 conflict
0x39aa73f3…34bb
0x34b655…2a6f
2 touches
0 conflicts
0x3be75497…9a3c
0x34b655…2a6f
2 touches
0 conflicts
0x56133b91…a672
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 0x08636046fc…69e60f
Audit this contract →
← previous block·next block →recent activity