← previous blocknext block →recent activity
Analyzing
Block #99,856,247
15 transactions · 12 stateful · 2026-08-28 08:56:00 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,856,247 · 15 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
1w03w04w110w211w312w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x010a35a5…1416
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xf85bdc12…5dff
0x34b655…2a6f
4 touches
1 conflict
0xfc24540b…6463
0x34b655…2a6f
4 touches
1 conflict
0x184a9b09…c825
0x34b655…2a6f
4 touches
1 conflict
0x62bb20db…431e
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 0x010a35a5a5…6f1416
Audit this contract →
← previous block·next block →recent activity