← previous blocknext block →recent activity
Analyzing
Block #100,740,642
36 transactions · 25 stateful · 2026-08-31 11:11:10 UTC
Parallelism
92/100
Blocked
40%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,740,642 · 36 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
1w02w04w05w17w19w011w012w114w019w122w223w125w127w234w235w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x78df73a4…acb6
0x34b655…2a6f
6 touches
3 conflicts
0x892daf6e…48d8
0x065c9d…c394
6 touches
3 conflicts
0xd7443f37…eb79
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
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 0x78df73a433…ccacb6
Audit this contract →
← previous block·next block →recent activity