← previous blocknext block →recent activity
Analyzing
Block #99,504,431
14 transactions · 14 stateful · 2026-08-27 03:12:02 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,504,431 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w09w110w211w312w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd6538fb…2b3f
0x34b655…2a6f
8 touches
6 conflicts
0x552b6853…3568
0x34b655…2a6f
6 touches
3 conflicts
0x19b34ad0…1b7c
0x34b655…2a6f
4 touches
1 conflict
0x27754bd4…96ae
0x34b655…2a6f
4 touches
1 conflict
0x424634a2…68da
0x34b655…2a6f
4 touches
1 conflict
0x5e8223c2…c242
0x34b655…2a6f
4 touches
1 conflict
0x63a6dacd…54a1
0x34b655…2a6f
4 touches
1 conflict
0x8a02d049…f481
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
6 conflicts on slot 0xdd6538fbaf…632b3f
Audit this contract →
← previous block·next block →recent activity