← previous blocknext block →recent activity
Analyzing
Block #99,183,234
19 transactions · 18 stateful · 2026-08-26 00:15:13 UTC
Parallelism
89/100
Blocked
22%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,183,234 · 19 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
1w08w09w111w113w114w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x1632f701…e67d
0x34b655…2a6f
4 touches
1 conflict
0x1ae9195f…9cb7
0x34b655…2a6f
4 touches
1 conflict
0x1da3ce84…9bb8
0x34b655…2a6f
4 touches
1 conflict
0x20afc93b…24c6
0x34b655…2a6f
4 touches
1 conflict
0x3dfbac71…3496
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x4b5d2bd6…9351
0x34b655…2a6f
4 touches
1 conflict
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 0xf3d10975b0…050d07
Audit this contract →
← previous block·next block →recent activity