← previous blocknext block →recent activity
Analyzing
Block #100,869,957
22 transactions · 17 stateful · 2026-08-31 22:02:04 UTC
Parallelism
91/100
Blocked
24%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,869,957 · 22 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w09w011w016w117w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40d6d1e9…131e
0x34b655…2a6f
4 touches
1 conflict
0x5c455afd…ce06
0x34b655…2a6f
4 touches
1 conflict
0xf4b2a427…0234
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x46cb45de…a566
0x188d58…ea8e
2 touches
0 conflicts
0x46cb45de…a567
0x188d58…ea8e
2 touches
0 conflicts
0x3e1e8e54…9c83
0x2a68ba…90c5
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
1 conflict on slot 0x40d6d1e99d…4f131e
Audit this contract →
← previous block·next block →recent activity