← previous blocknext block →recent activity
Analyzing
Block #99,483,038
12 transactions · 12 stateful · 2026-08-27 01:24:21 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,483,038 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w06w18w29w110w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0880f7c4…32fd
0x34b655…2a6f
6 touches
3 conflicts
0x9a100e05…c541
0x34b655…2a6f
6 touches
3 conflicts
0x95b9db78…ae3d
0x40c49f…2af0
4 touches
1 conflict
0x309be735…8510
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x757bd4b2…c8b1
0x34b655…2a6f
4 touches
1 conflict
0xb6ed511f…6b68
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
3 conflicts on slot 0x0880f7c4df…5832fd
Audit this contract →
← previous block·next block →recent activity