← previous blocknext block →recent activity
Analyzing
Block #100,455,495
9 transactions · 9 stateful · 2026-08-30 11:16:44 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,455,495 · 9 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
1w02w05w16w27w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd888a028…d306
0x34b655…2a6f
4 touches
1 conflict
0xd8917529…9e59
0x34b655…2a6f
4 touches
1 conflict
0x14e72ed1…9af6
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xfe45073e…6315
0x34b655…2a6f
4 touches
1 conflict
0x580f4794…c2f3
0x34b655…2a6f
4 touches
1 conflict
0x582c3466…2dc2
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…aaff
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 0xd888a028ac…74d306
Audit this contract →
← previous block·next block →recent activity