← previous blocknext block →recent activity
Analyzing
Block #100,093,966
19 transactions · 15 stateful · 2026-08-29 04:53:24 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.26
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,093,966 · 19 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
4w08w110w215w016w317w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb75d08b2…3e12
0x34b655…2a6f
4 touches
1 conflict
0xb9868b52…c77f
0x34b655…2a6f
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x631b4113…baa9
0x34b655…2a6f
4 touches
1 conflict
0x457a4030…329e
0x34b655…2a6f
2 touches
0 conflicts
0x613f1be8…2f1e
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 0xb75d08b251…823e12
Audit this contract →
← previous block·next block →recent activity