← previous blocknext block →recent activity
Analyzing
Block #99,188,104
12 transactions · 12 stateful · 2026-08-26 00:39:43 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,188,104 · 12 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
4w06w17w08w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5791ccc0…9a3d
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x02373c43…3cb3
0x34b655…2a6f
4 touches
1 conflict
0x65021fef…b735
0xa6afd3…d132
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x5e8223c2…c242
0x34b655…2a6f
2 touches
0 conflicts
0x6c3b70b7…b9a5
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 0x5791ccc08d…3d9a3d
Audit this contract →
← previous block·next block →recent activity