← previous blocknext block →recent activity
Analyzing
Block #100,463,048
14 transactions · 13 stateful · 2026-08-30 11:54:44 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,463,048 · 14 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
9w010w111w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ff576f3…716e
0x34b655…2a6f
6 touches
3 conflicts
0x266a6b2c…4376
0x34b655…2a6f
4 touches
1 conflict
0x266a6b2c…4377
0x34b655…2a6f
4 touches
1 conflict
0x96ed54e2…04ed
0x34b655…2a6f
4 touches
1 conflict
0xee75c266…f8c6
0x34b655…2a6f
4 touches
1 conflict
0xf238d135…0155
0x34b655…2a6f
4 touches
1 conflict
0x8046ca3c…f094
0x34b655…2a6f
2 touches
0 conflicts
0xd0f6f4f2…dffa
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 0x4ff576f39b…04716e
Audit this contract →
← previous block·next block →recent activity