← previous blocknext block →recent activity
Analyzing
Block #100,021,321
19 transactions · 17 stateful · 2026-08-28 22:47:43 UTC
Parallelism
84/100
Blocked
12%
Avg conflicts / tx
0.11
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,021,321 · 19 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
4w012w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d5c5d72…914b
0x34b655…2a6f
4 touches
1 conflict
0xb5c7c6aa…fdba
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x12f129f2…fe6b
0x2b46c0…1669
2 touches
0 conflicts
0x260cc5c4…bef0
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…1869
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…186a
0x2b46c0…1669
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 0x6d5c5d726f…33914b
Audit this contract →
← previous block·next block →recent activity