← previous blocknext block →recent activity
Analyzing
Block #100,630,512
18 transactions · 17 stateful · 2026-08-31 01:57:11 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,630,512 · 18 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
3w05w06w18w09w110w011w116w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x315e07b8…9823
0x34b655…2a6f
4 touches
1 conflict
0x44fb3f8d…7ec5
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x18a01188…42f0
0x851145…3f07
4 touches
1 conflict
0x1dedc384…ff57
0x851145…3f07
4 touches
1 conflict
0x2ce5d13f…f8a9
0x851145…3f07
4 touches
1 conflict
0x9210e826…1414
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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 0x315e07b806…529823
Audit this contract →
← previous block·next block →recent activity