← previous blocknext block →recent activity
Analyzing
Block #100,858,687
17 transactions · 16 stateful · 2026-08-31 21:05:23 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,858,687 · 17 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
2w03w14w09w110w213w214w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2d50773…c39e
0x34b655…2a6f
4 touches
1 conflict
0xef7bc6de…2aaf
0x34b655…2a6f
4 touches
1 conflict
0xf984d8ab…6e4f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
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
1 conflict on slot 0xe2d5077308…5ec39e
Audit this contract →
← previous block·next block →recent activity