← previous blocknext block →recent activity
Analyzing
Block #99,984,915
14 transactions · 14 stateful · 2026-08-28 19:44:22 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,984,915 · 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
3w05w17w08w09w210w311w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x451e482b…7e7d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xfbb59556…51d0
0x34b655…2a6f
4 touches
1 conflict
0xa11b60f7…8e8b
0x34b655…2a6f
4 touches
1 conflict
0x4d7d1066…4e72
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 0x451e482b59…427e7d
Audit this contract →
← previous block·next block →recent activity