← previous blocknext block →recent activity
Analyzing
Block #96,610,106
9 transactions · 8 stateful · 2026-08-16 22:33:42 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,610,106 · 9 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
2w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c09c53e…64b4
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x4f5ede92…319b
0x34b655…2a6f
4 touches
1 conflict
0xd4d78b50…ca0a
0x3bd359…433a
2 touches
0 conflicts
0xd71961d0…4538
0x3ef3d8…d9ae
2 touches
0 conflicts
0xd71961d0…4539
0x3ef3d8…d9ae
2 touches
0 conflicts
0xfc619ad3…8d5a
0x3ef3d8…d9ae
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 0x7c09c53e5b…3864b4
Audit this contract →
← previous block·next block →recent activity