← previous blocknext block →recent activity
Analyzing
Block #100,627,483
21 transactions · 19 stateful · 2026-08-31 01:41:56 UTC
Parallelism
71/100
Blocked
37%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,627,483 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w110w211w316w417w218w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1c20de1…afc3
0x34b655…2a6f
10 touches
10 conflicts
0xead15497…1dbe
0x34b655…2a6f
8 touches
6 conflicts
0x7d0eaae2…60b7
0x34b655…2a6f
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xe720a4c6…8eb0
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
10 conflicts on slot 0xb1c20de18c…84afc3
Audit this contract →
← previous block·next block →recent activity