← previous blocknext block →recent activity
Analyzing
Block #100,607,437
23 transactions · 17 stateful · 2026-08-31 00:01:06 UTC
Parallelism
87/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,607,437 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w08w09w010w018w119w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ed1f9d0…fc7f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x50951f37…219c
0x3bd359…433a
4 touches
1 conflict
0xf8896813…3c3b
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x1fb8364c…c10d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
3 conflicts on slot 0x5ed1f9d00b…62fc7f
Audit this contract →
← previous block·next block →recent activity