← previous blocknext block →recent activity
Analyzing
Block #100,154,612
14 transactions · 14 stateful · 2026-08-29 09:58:53 UTC
Parallelism
79/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,154,612 · 14 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
1w02w16w17w18w110w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xedee7e09…6888
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x61571888…b392
0x34b655…2a6f
4 touches
1 conflict
0x72550c77…bbfd
0x34b655…2a6f
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0xd5b10148…e636
0x1b6862…e19c
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 0xedee7e090f…056888
Audit this contract →
← previous block·next block →recent activity