← previous blocknext block →recent activity
Analyzing
Block #100,918,937
16 transactions · 16 stateful · 2026-09-01 02:08:26 UTC
Parallelism
81/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,918,937 · 16 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
1w02w13w25w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x4a39a2a4…857b
0x34b655…2a6f
4 touches
1 conflict
0x1589612f…7222
0x065c9d…c394
2 touches
0 conflicts
0x250186ca…427c
0x065c9d…c394
2 touches
0 conflicts
0xaa700fda…2466
0x065c9d…c394
2 touches
0 conflicts
0xf04e07fd…7ae4
0x065c9d…c394
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
3 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity