← previous blocknext block →recent activity
Analyzing
Block #100,056,036
14 transactions · 12 stateful · 2026-08-29 01:42:27 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,056,036 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xb240b520…a88a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x20bcad45…9cea
0x34b655…2a6f
2 touches
0 conflicts
0x3c0e1ae4…59f1
0x34b655…2a6f
2 touches
0 conflicts
0x40cc5368…0387
0x34b655…2a6f
2 touches
0 conflicts
0x4b24225e…5a6b
0x34b655…2a6f
2 touches
0 conflicts
0x5871b087…587d
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
1 conflict on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity