← previous blocknext block →recent activity
Analyzing
Block #100,874,793
18 transactions · 9 stateful · 2026-08-31 22:26:24 UTC
Parallelism
89/100
Blocked
11%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,874,793 · 18 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
16w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38befc08…20c8
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xde54926c…1c87
0x34b655…2a6f
4 touches
1 conflict
0x121487b3…7919
0x065c9d…c394
2 touches
0 conflicts
0x5f77d607…2c84
0x065c9d…c394
2 touches
0 conflicts
0x5f7d3164…b6d0
0x065c9d…c394
2 touches
0 conflicts
0xaad6be10…0801
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 0x38befc0864…cc20c8
Audit this contract →
← previous block·next block →recent activity