← previous blocknext block →recent activity
Analyzing
Block #100,983,829
16 transactions · 13 stateful · 2026-09-01 07:34:51 UTC
Parallelism
81/100
Blocked
23%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,983,829 · 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
2w08w09w112w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x953517cb…cdec
0x34b655…2a6f
6 touches
3 conflicts
0xd2fd6de4…1729
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4e58deff…c5d0
0x34b655…2a6f
4 touches
1 conflict
0xa7dcd6d9…a1ba
0x34b655…2a6f
4 touches
1 conflict
0x1a3d2527…8ca0
0x34b655…2a6f
4 touches
1 conflict
0x845ec8b0…c1af
0x34b655…2a6f
2 touches
0 conflicts
0x98862f54…62ca
0x34b655…2a6f
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 0x953517cb5b…8dcdec
Audit this contract →
← previous block·next block →recent activity