← previous blocknext block →recent activity
Analyzing
Block #100,237,208
14 transactions · 12 stateful · 2026-08-29 16:54:40 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,237,208 · 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
2w03w14w28w09w110w312w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70e677f5…e3bd
0x34b655…2a6f
4 touches
1 conflict
0x71a923ba…41eb
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf7d258c1…286a
0x34b655…2a6f
4 touches
1 conflict
0x3952b40f…4c8c
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 0x70e677f5c0…90e3bd
Audit this contract →
← previous block·next block →recent activity